ddd-architect

Domain-Driven Design architecture is enforced through automated validation of layer separation, dependency direction checks, and structural patterns. This Skill detects violations like improper dependencies between Presentation, Application, Domain, and Infrastructure layers, helping maintain clean architecture as code evolves.

Yes, the Skill scaffolds standard DDD structure automatically when creating new features or modules. It generates organized folders for Domain, Application, and Infrastructure layers, plus Entities, ValueObjects, and Repositories, reducing manual setup time and ensuring consistency.

Data Access Layer (DAL) separation isolates database logic from domain logic, enforcing that Infrastructure depends on Domain, never the reverse. This prevents tight coupling, improves testability, and ensures your domain model stays independent of persistence implementation details.

Dependency direction validation checks that your codebase follows the correct flow: Presentation → Application → Domain, and Infrastructure → Domain. The Skill warns about violations during architecture reviews and new feature creation, catching problematic dependencies early.

Run architecture validation during new feature scaffolding and architecture reviews to prevent violations from accumulating. Early detection catches improper dependencies before they become entrenched, keeping your codebase aligned with DDD principles and scalable design.

Your codebase should have a clear folder structure and defined layers (Domain, Application, Infrastructure, Presentation). The Skill works best when you've identified domain artifacts like Entities, ValueObjects, and Repositories that need architectural validation.