clean-architecture

Structure your software project using Clean Architecture by separating Domain, Application, Infrastructure, and Presentation layers. This Skill guides implementing DDD tactical patterns like Entities, Aggregates, and Repositories to enforce inward dependencies and deliver modular, testable code.

The best way to refactor into hexagonal architecture is analyzing current boundaries and applying the Dependency Rule. This Skill outlines initial structures and decision trees for ports and adapters, reducing architectural drift during refactoring.

You need CQRS and domain events when separating command and query responsibilities for scalable software. This Skill provides guidance on applying these patterns alongside SOLID principles during design reviews and new feature development across domains.

You can use onion architecture for existing codebases by enforcing layered boundaries and inward dependencies. This Skill identifies anti-patterns and provides practical project structures to resolve decision fatigue and reduce coupling.

Architectural drift happens when layered boundaries are not enforced, and SOLID principles prevent it by guiding consistent pattern choices. This Skill enforces inward dependencies and provides anti-pattern catalogs to maintain modular software.