Apply Domain-Driven Design patterns to model aggregates and bounded contexts.
npx skills add https://github.com/iceflower/agent-skills --skill ddd-iceflower
Please help me install this Agent Skill. Skill: ddd Source: https://github.com/iceflower/agent-skills/tree/main/ddd Command: npx skills add https://github.com/iceflower/agent-skills --skill ddd-iceflower
Domain-Driven Design patterns provide a structured approach to modeling complex business domains, aligning software with domain knowledge using entities, value objects, aggregates, repositories, domain services, domain events, and bounded contexts.
Define a simple Order-like aggregate, establish invariants, and map bounded contexts to demonstrate end-to-end domain modeling.
High-intent search queries and answers about installing and using this skill.
To model aggregates in domain-driven design, you group entities and value objects under an aggregate root, which enforces invariants and transactional boundaries. This ensures consistency within the aggregate while exposing controlled access to internal components.
The best way to handle communication between bounded contexts is through domain events. Domain events support eventual consistency by allowing aggregates in separate contexts to react to state changes asynchronously without tight coupling.
Entities possess a distinct identity that persists over time, while value objects are defined solely by their attribute values. Shaping a domain model requires using entities for lifecycle tracking and value objects for descriptive, immutable concepts.
Use domain services for complex business domains when logic does not naturally fit within a single entity or value object. Application services coordinate use cases, manage repositories, and orchestrate domain objects without containing business rules.
Domain-driven design is specifically structured for systems with evolving requirements and multiple aggregates. It uses bounded contexts and ubiquitous language to manage complexity, ensuring the software architecture adapts to changing business rules.
Repositories and factories define persistence boundaries in DDD by abstracting data access and object creation. Repositories provide collection-like access to aggregates, while factories encapsulate complex instantiation to maintain valid state.
pohlai88Model software around business domains using bounded contexts and aggregates.
DynokostyaApply Domain-Driven Design tactical patterns to Python codebases.
NickCrewApply CQRS and Event Sourcing patterns for scalable auditing and event replay.
gutierrezp22Enforce hexagonal architecture layer boundaries between Domain, Application, and Infrastructure in Java services.
