What problem does it solve?
This Skill prevents AI-assisted code changes from creating regressions, oversized files, unclear boundaries, hidden coupling, and unverified architectural debt.
Core Features & Use Cases
- AI-safe architecture doctrine: Applies SOLID, separation of concerns, Clean Architecture, Clean Code, DRY, KISS, and YAGNI.
- Machine-enforced guardrails: Enforces file-size thresholds, import-boundary checks, verification gates, and traceability between decisions and implementation.
- Refactoring guidance: Provides a structured six-wave playbook for stabilizing tests, decomposing god files, organizing bounded contexts, and strengthening architectural boundaries.
- Debugging discipline: Requires documented research before intensive debugging of dependency, framework, native, or version-specific issues.
- Use Case: Apply it when starting a project, editing production code, planning a refactor, or dealing with a codebase that is becoming difficult and risky to change.
Quick Start
Use the software-architecture skill to assess the current codebase, identify architectural risks, and define an enforced plan for improving its structure.