domain-driven-design
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.
- Version
- 1.4.0
- License
- MIT
Pinned to revision 4f7124e6049e, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/domain-driven-design/SKILL.md
- skills/domain-driven-design/references/bounded-contexts.md
- skills/domain-driven-design/references/building-blocks.md
- skills/domain-driven-design/references/domain-events.md
- skills/domain-driven-design/references/repositories-factories.md
- skills/domain-driven-design/references/strategic-design.md
- skills/domain-driven-design/references/ubiquitous-language.md
Every link opens the file at its source, pinned to the revision this page describes.