architecture-patterns

To identify the architecture pattern, analyze the repository structure to detect signatures of Vertical Slice, Clean Architecture, CQRS, or N-Tier. This provides concise explanations of the pattern and validates alignment with documented conventions.

The best way to validate code against CONVENTIONS.md is to compare the repository structure against the chosen pattern. This enforces alignment, supports auditability through review checklists, and clarifies domain or handler responsibilities.

You need Vertical Slice or CQRS when separating read/write operations or organizing by feature rather than layers. This clarifies responsibilities within handler contexts and ensures alignment with the project's documented architectural conventions.

Yes, you can use this during onboarding to explain the existing N-Tier or Clean Architecture pattern. It serves as a reference to help developers understand the chosen structure and compare it against CONVENTIONS.md.

Yes, it supports architecture pattern validation for domain handlers by clarifying their specific responsibilities. It enforces alignment of handler code against the chosen pattern and checks compliance with CONVENTIONS.md.