principle-clean-architecture

What problem does it solve?

This Skill helps you prevent architectural erosion by enforcing clean boundaries so business logic stays independent of frameworks, databases, and other external concerns.

Core Features & Use Cases

• Dependency Rule Enforcement: Keeps source-code dependencies pointing inward so inner layers remain framework-agnostic.
• Ports & Adapters (Hexagonal Architecture): Separates interfaces (ports) from implementations (adapters) to make the domain testable and swappable.
• Domain Purity & Boundary Crossing Guidance: Ensures the domain does not import HTTP/SQL/ORM/JSON/wall-clock concerns, with outer layers translating across well-defined structures.
• Practical Refactoring Checklist: Detects drift smells like repositories returning ORM objects or use cases importing request/response types.

Quick Start

Ask the assistant to apply the dependency rule and propose a layer breakdown (domain/application/infrastructure/framework) for your service while identifying which components must become ports and adapters.