review-architecture

Architecture review for modular monoliths validates DDD patterns and Clean Architecture boundaries by checking inward dependencies across Domain, Application, Infrastructure, and Presentation layers to ensure proper layer isolation and separation of concerns.

ADR guidelines like ADR-0001 and ADR-0011 enforce specific architectural decisions for DDD pattern compliance. They validate domain events, cross-module contracts, and module boundaries to prevent architectural drift and maintain structural integrity across the codebase.

Enforce layer isolation during a PR review by verifying inward dependencies and cross-module contract compliance using structured feedback templates to validate separation of concerns across Domain, Application, Infrastructure, and Presentation layers.

Yes, the architecture review skill verifies Onion Architecture conventions by analyzing dependency directions and layer boundaries to ensure dependencies point inward toward the domain core and maintain proper infrastructure and application separation.

Use domain events in a modular monolith architecture to handle cross-module communication and enforce bITdevKit conventions, with the architecture review skill validating proper event usage to ensure loose coupling and maintain clean architectural boundaries.

The best way to prevent architectural drift is conducting regular architecture reviews that verify DDD patterns, Clean Architecture boundaries, and ADR compliance to identify dependency violations and cross-module contract issues early during refactoring and PR discussions.