domain-driven-design

Domain-driven design tactical patterns are enforced by defining aggregates, value objects, and domain boundaries to ensure domain logic is expressive and cohesive. The Skill configures resolution via .lattice/config.yaml and defaults in references/defaults.md.

Modeling invariants within a single bounded context requires defining clear aggregate boundaries and ownership rules. This approach uses domain events for cross-boundary coordination across entities and domain services.

Domain events for cross-boundary coordination are needed when aligning code with ubiquitous language and managing interactions between distinct aggregates. They ensure domain logic remains cohesive while enabling cross-entity communication.

Yes, this DDD Skill supports language adaptation and repository patterns via a config-driven approach. It uses .lattice/config.yaml and provided defaults to adapt tactical patterns and guidance for your domain model.

Align ubiquitous language with rich domain objects by turning business concepts into entities, value objects, and domain services. This ensures the domain model explicitly defines aggregates and boundaries.

Yes, you can apply DDD tactical patterns to an existing domain model to enforce aggregates, value objects, and domain boundaries. This resolves complexity by explicitly defining invariants and ownership across domain services.