architecture-patterns

You should choose Clean Architecture when strict separation of concerns is critical, placing business logic in the domain layer with dependencies flowing inward. Alternatively, Vertical Slice organizes code by feature rather than technical layers, which can reduce cross-cutting dependencies for smaller .NET applications.

You can review .NET code for pattern compliance using a structured checklist that verifies business logic placement in the domain layer, ensures dependencies flow correctly, and validates adherence to documented conventions in .planning/CONVENTIONS.md.

Vertical Slice organizes .NET code by feature rather than technical layers, reducing cross-cutting dependencies. Clean Architecture enforces strict layering with business logic in the domain layer and dependencies flowing inward, prioritizing separation of concerns over feature encapsulation.

You should use the CQRS pattern in a .NET project when you need to separate read and write operations for improved scalability and performance. This Skill provides reference material to help you evaluate if CQRS fits your application's architectural requirements and complexity.

To ensure your .NET project adheres to documented architectural conventions, review your code against the guidelines in .planning/CONVENTIONS.md. This Skill provides a structured checklist to verify pattern compliance, separation of concerns, and resilience during code reviews.