What problem does it solve? Business logic often becomes entangled with frameworks, databases, and delivery mechanisms, making systems untestable and forcing rewrites when infrastructure changes. This Skill applies Robert C. Martin's Clean Architecture principles to keep business rules independent of volatile technical details. ## Core Features & Use Cases - Dependency Rule Enforcement: Organize code into concentric circles (Entities, Use Cases, Interface Adapters, Frameworks) where source dependencies always point inward. - Component and SOLID Guidance: Apply REP, CCP, CRP, ADP, SDP, SAP component principles plus the five SOLID principles with concrete code examples. - Architecture Scoring and Diagnostics: Score an architecture 0-10 using a seven-row diagnostic and get specific inversion fixes for each failure. - Use Case: When reviewing a codebase where business rules live in controllers and ORM models, use this Skill to identify outward dependencies, define boundary interfaces, and restructure into testable use case interactors. ## Quick Start Review my project structure and tell me which layers violate the Dependency Rule and how to fix each violation.