Domain-Driven Design

Agents already know domain-driven design. What they lack is the domain: the terms, rules, and boundaries of this business. DOMAIN.md supplies that. It records the ubiquitous language, the model, and the rules and invariants, so every later task starts from the same model instead of re-deriving one from code.

This skill writes and maintains DOMAIN.md at the repository root. Treat the user as the domain expert: extract rules through concrete scenarios and write down only what they confirm. The skill does not change code. Bringing the implementation in line with the model is separate work that reads DOMAIN.md.

references/domain-driven-design.md is this skill's definition of domain-driven design. Read it: