domain-driven-design
domain driven design
What it does
- The language emerges from deep collaboration, not a glossary bolted on after the fact
- If a concept is hard to name, the model is likely wrong -- naming difficulty is a design signal
- Technical jargon (DataProcessor vs. ClaimAdjudicator) hides domain logic from the experts who could correct it
- Different bounded contexts may use the same word with different meanings -- and that is fine
- A bounded context is not a microservice -- it is a linguistic and model boundary that may contain multiple services
- Context boundaries often align with team boundaries (Conway's Law)
- The nine context mapping patterns describe political and technical relationships between teams
Requirements & configuration
- Factories are warranted for complex rules or multi-part assembly; a two-field Value Object just needs a constructor
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
domain-driven-design FAQ
What does the domain-driven-design skill do?
Model software around the business domain using bounded contexts, aggregates, and ubiquitous language. Use when the user mentions "domain modeling", "bounded context", "aggregate root", "ubiquitous language", "anti-corruption layer", "context mapping", "domain events", "strategic design", "the code doesnt match the business", or "how do we split this big system". Also trigger when breaking a monolith into services, defining service boundaries, or aligning code structure with business processes. Covers entities vs value objects, domain events, and context mapping strategies. For architecture layers, see clean-architecture. For complexity, see software-design-philosophy. The language emerges from deep collaboration, not a glossary bolted on after the fact If a concept is hard to name, the model is likely wrong -- naming difficulty is a design signal
What does domain-driven-design require?
Factories are warranted for complex rules or multi-part assembly; a two-field Value Object just needs a constructor
How do I install domain-driven-design?
Run: npx -y skills add https://github.com/wondelai/skills --skill domain-driven-design --agent claude-code — the source lives at github.com/wondelai/skills.
Maintain domain-driven-design?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[domain-driven-design on getagentictools](https://getagentictools.com/skills/wondelai-skills-domain-driven-design?ref=badge) npx agentictools info skills/wondelai-skills-domain-driven-design The second line is the CLI lookup for this page — handy in READMEs and docs.
