Codebase Design
Design or improve module interfaces using deep-module heuristics.
Install
npx skills add stevesolun/ctx --skill codebase-design -g -a claude-code -y- Repository
- stevesolun/ctx589
- Category
- Design
- Updated
- 21d ago
- License
- MIT
- Context cost
- Lightabout 598 tokens
- Runs scripts
- No, instructions only
What it does
Design or improve module interfaces using deep-module heuristics. Use when deciding where a seam belongs, reducing caller-facing complexity, improving testability or navigability, or comparing module designs.
Codebase Design
Seek deep modules: substantial useful behavior behind a small, stable interface. Use the concepts below as design lenses, while matching the repository's established domain language.
Working vocabulary
- Module: a coherent unit with an interface and implementation, at any scale.
- Interface: everything callers must know, including invariants and failure modes, not just a type signature.
- Seam: a location where behavior can vary without editing its callers.
- Adapter: an implementation that connects at a seam.
- Depth: useful capability relative to interface complexity.
- Leverage: capability gained by callers; locality: change and knowledge concentrated for maintainers.
Translate these terms to the project's vocabulary when that makes the design clearer. Consistency with the codebase is more valuable than enforcing a private lexicon.
Design workflow
- Map representative callers, responsibilities, dependencies, and existing contracts.
- Look for coordination or policy that can move behind a smaller interface.
- Place seams where variation, ownership, or test isolation justifies them.
- Compare alternatives when the choice is consequential.
- Validate the candidate with representative caller code and tests.
