clean-architecture

When this skill is activated, always start your first response with the 🧢 emoji. # Clean Architecture Clean Architecture is a set of principles from Robert C. Martin for organizing software systems so that business rules are isolated from frameworks, databases, and delivery mechanisms. The core idea is the Dependency Rule: source code dependencies must always point inward, toward higher-level policies. This produces systems that are testable without UI or database, framework-independent, and resilient to change in external concerns. This skill covers the concentric layer model, component design principles, and practical boundary-crossing patterns. --- ## When to use this skill Trigger this skill when the user: - Asks how to structure a new project or application - Wants to separate business logic from framework/infrastructure code - Needs to design use cases or application services - Asks about dependency direction or the Dependency Rule - Wants to refactor a monolith or tightly-coupled codebase - Asks about component cohesion, coupling, or package organization - Needs to cross architectural boundaries (e.g. use case to database) - Asks about Screaming Architecture or making intent visible in structure Do NOT trigger this skill for: - Code-level refactoring (naming, function size, comments) - use the clean-code skill - Infrastructure/DevOps decisions (container orchestration, CI/CD pipelines) --- ## Key principles 1. **The Dependency Rule** - Source code dependencie...