clean-architecture
Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.
- Version
- 1.4.0
- License
- MIT
Pinned to revision 4f7124e6049e, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/clean-architecture/SKILL.md
- skills/clean-architecture/references/adapters-frameworks.md
- skills/clean-architecture/references/boundaries.md
- skills/clean-architecture/references/component-principles.md
- skills/clean-architecture/references/dependency-rule.md
- skills/clean-architecture/references/entities-use-cases.md
- skills/clean-architecture/references/solid-principles.md
Every link opens the file at its source, pinned to the revision this page describes.