メニュー
Find deep-module opportunities in a codebase. Use when the user wants to improve architecture, refactor, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when refactoring code, identifying refactor candidates, or improving design after tests are green.
Use when discussing levels of abstraction, composed method, SLAP, stepdown rule, or mixed abstraction levels within a function.
Use when refactoring into deep modules, choosing seams, classifying dependencies, deciding adapter strategy, or planning tests around a refactor.
Use when designing interfaces, comparing interface alternatives, applying Design It Twice, or exploring interfaces for a module.
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
Use when discussing modules, interfaces, implementation, depth, seams, adapters, leverage, locality, or code design terminology.
| name | review-architecture |
| description | Find deep-module opportunities in a codebase. Use when the user wants to improve architecture, refactor, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable. |
Surface architectural friction and propose deep-module opportunities — refactors that turn shallow modules into deep ones.
Load skill: code-design. Load skill: deep-modules.
Present a numbered list of deep-module opportunities. For each candidate:
Do NOT propose interfaces yet. Ask the user: "Which of these would you like to explore?"
Once the user picks a candidate, load and follow explore-design-space. Explore the selected deep-module opportunity as the plan or design under review.
