Enforce DDD aggregate boundaries and invariants during domain design reviews.
npx skills add https://github.com/j5ik2o/okite-ai --skill aggregate-design
Please help me install this Agent Skill. Skill: aggregate-design Source: https://github.com/j5ik2o/okite-ai/tree/main/.agent/skills/aggregate-design Command: npx skills add https://github.com/j5ik2o/okite-ai --skill aggregate-design
Designing domain models that keep aggregate boundaries and invariants is challenging and error-prone. aggregate-design provides structured, enforceable guidance for clustering related domain objects into stable aggregates and for ensuring the aggregate root maintains true invariants.
Start by auditing current aggregates to identify boundary violations and invariants, then update the domain model accordingly.
High-intent search queries and answers about installing and using this skill.
To design aggregate boundaries with true invariants, you must cluster related domain objects into stable aggregates and enforce Design by Contract constraints within the aggregate root. This ensures boundary access and immutability considerations are strictly maintained.
Evans Rules and Vernon's Rules guide repository access and boundary maintenance by enforcing that inter-aggregate references rely on identity rather than direct object references. This encapsulation reduces coupling and clarifies domain boundaries across services.
Auditing domain models for aggregate boundary violations involves reviewing current aggregate clusters to identify broken invariants and improper root access. You then refactor the domain model to align with strict boundary maintenance and Design by Contract principles.
You should refactor aggregate boundaries during a design review when inter-aggregate coupling increases or invariants are violated. Restructuring aggregate roots and boundary access patterns restores domain model clarity and enforces immutability constraints.
Aggregate design principles apply directly to refactoring domain models across multiple services. The guidance enforces consistent aggregate boundaries, root-entity access patterns, and invariant checks regardless of the service scope.
An aggregate root fails to enforce domain invariants when boundary access patterns are violated or related objects are improperly clustered. Applying Design by Contract constraints and strict root-entity encapsulation resolves these invariant failures.
shafibabarDefine Domain-Driven Design Aggregate boundaries using invariant-testing decision trees.
EntelligentsiaOrganize business objects into Entity, Value Object, and Aggregate patterns.
anton-abyzovManage Avro, Protobuf, and JSON Schema compatibility and evolution via Confluent Schema Registry.
ricableDecompose monolithic structures into modular bounded contexts with a microkernel pattern.
