Refactoring
Code restructuring and optimization
clean-names
by ertugrul-dmr
Use when naming, renaming, or fixing names of variables, functions, classes, or modules in Python. Enforces Clean Code principles—descriptive names, appropriate length, no encodings.
airline-cargo-optimization
by kishorkukreja
When the user wants to optimize airline cargo operations, manage air freight, or improve cargo revenue. Also use when the user mentions "air cargo optimization," "cargo capacity management," "freight yield management," "ULD optimization," "cargo routing," "air freight network," or "belly cargo management." For passenger operations, see hotel-inventory-management (for yield management concepts). For tour operations, see tour-operations.
dock-door-assignment
by kishorkukreja
When the user wants to optimize dock door assignments, schedule truck arrivals, or minimize yard congestion. Also use when the user mentions "dock scheduling," "door assignment," "yard management," "truck scheduling," "cross-dock optimization," or "appointment scheduling." For cross-docking operations, see cross-docking. For yard management, see yard-management.
tdd
by TechDufus
"Systematic TDD methodology for writing tests first. Use when implementing features or fixes with OMC_TDD_MODE enabled, when unsure how to structure tests, or when test-first discipline needs reinforcement. Triggers on: 'tdd', 'test first', 'test driven', 'red green refactor'."
sound-design-film
by guia-matthieu
"Apply Walter Murch's legendary film sound principles to marketing video, creating emotionally resonant audio that audiences feel without consciously noticing. Use when: Designing sound for brand films and documentaries; Creating emotional impact in video ads; Layering music, effects, and voice effectively; Building immersive soundscapes for content; Elevating production value through audio"
python-clean-code
by ertugrul-dmr
Use when writing, fixing, editing, reviewing, or refactoring any Python code. Enforces Robert Martin's complete Clean Code catalog—naming, functions, comments, DRY, and boundary conditions.
clean-general
by ertugrul-dmr
Use when writing, fixing, editing, or reviewing Python code quality. Enforces Clean Code's core principles—DRY, single responsibility, clear intent, no magic numbers, proper abstractions.
pueue-job-orchestration
by terrylica
Pueue universal CLI telemetry and job orchestration. TRIGGERS - run on bigblack, run on littleblack, queue job, long-running task, cache population, batch processing, GPU workstation, pueue callback, pueue delay, pueue priority.
optimise-seo
by mblode
Optimises SEO for Next.js App Router apps including sitemaps, meta tags, structured data, canonical URLs, Core Web Vitals, and programmatic SEO. Use when asked to improve SEO, add sitemap.xml, fix meta tags, add structured data, set canonical URLs, improve Core Web Vitals, audit SEO, or build SEO pages at scale. Performs no visual redesigns.
refactor
by AsiaOstrich
"[UDS] Guide refactoring decisions and strategy selection"
agent-orchestration-multi-agent-optimize
by benjaminasterA
"Optimize multi-agent systems with coordinated profiling, workload distribution, and cost-aware orchestration. Use when improving agent performance, throughput, or reliability."
cli-ux-improver
by proflead
Improve CLI help, errors, and output. Use when a mid-level developer needs to make a CLI friendlier.
advisor-triggers
by akaszubski
Detects when user requests warrant critical analysis via /advise command
code-simplifier
by steveclarke
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
code-refactoring
by baz-scm
The practice of restructuring and simplifying code continuously – reducing complexity, improving design, and keeping codebases clean.
team-collaboration
by baz-scm
Working effectively with others in coding projects – including code reviews, clear communication, and contributing to shared or open-source codebases.
code-readability
by baz-scm
Writing clean, understandable, and self-documenting code that is easy to review and maintain over time.
container-loading-optimization
by kishorkukreja
When the user wants to optimize container loading, load shipping containers efficiently, or maximize container utilization. Also use when the user mentions "container packing," "FCL optimization," "LCL consolidation," "container stuffing," "cargo optimization," "shipping container loading," or "container utilization." For pallet-level optimization, see pallet-loading. For general 3D packing, see 3d-bin-packing.
fuel-distribution
by kishorkukreja
When the user wants to optimize retail fuel distribution, manage gasoline and diesel delivery, or plan petroleum product logistics. Also use when the user mentions "gas station supply," "fuel delivery routing," "petroleum retail," "tank truck scheduling," "fuel terminal operations," "wholesale fuel distribution," or "retail fuel network." For upstream, see drilling-logistics. For midstream, see energy-logistics.
code-smell-detector
by ArabelaTso
Identify and report code smells indicating poor design or maintainability issues in Python code, including duplicate code, magic numbers, hardcoded values, God classes, feature envy, inappropriate intimacy, data clumps, primitive obsession, and long parameter lists. Use when conducting code quality audits, preparing for refactoring, improving codebase maintainability, or performing design reviews. Produces markdown reports with severity ratings, locations, descriptions, and specific refactoring recommendations with before/after examples. Triggers when users ask to find code smells, identify design issues, suggest refactorings, improve code quality, or detect maintainability problems.
ask-questions-if-underspecified
by hainamchung
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
marketplace-liquidity
by liqiongyu
"Diagnose and improve marketplace liquidity (match rate/fill rate, time-to-match, reliability) by segment. Produces a Marketplace Liquidity Management Pack: liquidity definition + metric tree, fragmentation map, segment scorecard, supply/demand bottleneck diagnosis, experiment backlog, measurement plan, and operating cadence. Use for Growth teams running two-sided marketplaces."
refactoring
by cosmix
Restructures existing code to improve readability, maintainability, and performance without changing external behavior. USE WHEN: Restructuring code without changing behavior, extracting methods/classes, removing duplication, applying design patterns, improving code organization, reducing technical debt. DO NOT USE: For bug fixes (use /debugging), for adding tests (use /testing), for new features (implement directly). TRIGGERS: refactor, restructure, rewrite, clean up, simplify, extract, inline, rename, move, split, merge, decompose, modularize, decouple, technical debt, code smell, DRY, SOLID, improve code, modernize, reorganize.
readwise-prune
by edwinhu
Clean up stale Readwise Reader documents. Use when the user wants to declutter their reading library, remove old unread articles, or manage Reader inbox. Triggers on "clean up readwise", "prune reader", "delete old articles", "declutter reading list".