What problem does it solve?
When refactoring code, splitting files, or redesigning system architecture, developers often create circular dependencies, oversized files, and tangled module boundaries. This Skill enforces disciplined architecture rules so structural changes stay controlled, verifiable, and reversible.
Core Features & Use Cases
- SOLID and Layering Enforcement: Applies single responsibility, open-closed, and dependency inversion principles, with strict outer-to-inner dependency direction (UI → Service → Repository) and zero circular dependencies.
- Code Organization Rules: Promotes feature-based grouping, shared logic extraction only after three repetitions, and hard size limits (files/classes split at 400 lines, functions at 60 lines).
- Controlled Change Strategy: Requires mapping current-to-target dependency graphs before coding, assessing blast radius, and splitting large refactors into independently verifiable and rollbackable steps.
- Use Case: When extracting a component from a 600-line module, the Skill guides you to draw the dependency path first, split by feature, verify no circular imports remain, and confirm each step passes delivery checks.
Quick Start
Ask the AI to refactor a large module or restructure your project architecture, and it will apply these architecture rules and delivery checks.