What problem does it solve? Software systems often become tangled when business logic mixes with frameworks, databases, and UI code, making them hard to test, change, and maintain. This Skill provides 42 prioritized rules from Robert C. Martin's Clean Architecture to guide system design, code review, and refactoring toward proper separation of concerns. ## Core Features & Use Cases - 42 Prioritized Rules Across 8 Categories: Covers dependency direction, entity design, use case isolation, component cohesion, boundaries, interface adapters, framework isolation, and testing architecture, each tagged by architectural impact. - Detailed Reference Files with Code Examples: Every rule includes incorrect vs. correct implementations in multiple languages (TypeScript, Java, Python, Go, C#) with explanations of benefits and trade-offs. - Use Case: When reviewing a codebase where controllers contain business logic and entities import ORM annotations, consult the relevant rules to identify violations and apply patterns like thin controllers, dependency inversion, and persistence-ignorant entities. ## Quick Start Review my order processing module against Clean Architecture principles and identify dependency direction violations.
