What problem does it solve?
This Skill helps determine whether modules are divided in the right places, preventing shallow pass-through components, duplicated knowledge, and tightly coupled boundaries that make changes harder to understand and maintain.
Core Features & Use Cases
- Boundary Evaluation: Analyze whether related responsibilities should be merged and unrelated responsibilities should be separated.
- Decomposition Guidance: Identify merge signals, split signals, conjoined methods, and opportunities for a genuine third abstraction.
- Knowledge Ownership Analysis: Check whether each boundary fully encloses the design decisions and shared information it owns.
- Use Case: Apply it when deciding whether to split a large class, merge tightly coupled modules, or review a decomposition where changes repeatedly span multiple components.
Quick Start
Use the module-boundaries skill to review the architecture and boundary decisions in the specified file or module path.