deep-module-design
Installation
SKILL.md
Deep Module Design
Module-level design for code that is getting harder to change. A deep module gives callers a lot of behaviour behind a small interface; a shallow one makes them learn almost as much as it does. This skill measures where a codebase is shallow, ranks the places where deepening would pay back, writes the review, and then designs the replacement interface at least twice before anyone writes it. The goal: callers get a lot done through very little surface, a change stays inside one module, and tests exercise the same interface callers use.
When to use this skill
- Designing a new module and wanting its interface right before callers multiply
- "Improve the architecture of this codebase" — find and rank deepening opportunities
- A change keeps touching five files for one business rule
- Tests are brittle because they reach past interfaces into internals
- Layers that only forward calls — services that call repositories that call clients, each adding nothing
- Choosing between interface proposals for the same module