What problem does it solve?
This skill prevents business logic from being accidentally misplaced across controllers, application services, and infrastructure, which otherwise leads to untestable code, leaky dependencies, and inconsistent behavior across delivery mechanisms.
Core Features & Use Cases
- Define enforceable responsibilities across presentation, application, domain, and infrastructure so each layer owns what it should and rejects what it must not.
- Codify dependency direction rules (domain inward, never domain→infrastructure) to ensure architecture remains stable even as frameworks and storage technologies change.
- Specify transaction, validation, and exception boundaries so invariants live in the domain, transactions are orchestrated in the application layer, and infrastructure errors are mapped at the adapter boundary.
Real-world use case: while reviewing a change that adds a new route, handler, repository, or external adapter, apply these rules to move business decisions into domain or application orchestration correctly and to isolate persistence details behind domain ports.
Quick Start
Ask an AI to generate a layered architecture plan for your feature by mapping each new class or file to Presentation, Application, Domain, or Infrastructure and by producing a dependency, transaction, and exception-mapping checklist that matches the non-negotiable rules.
