This skill loads a compact rule set inspired by Vaughn Vernon’s Domain-Driven Design Distilled. It tells a coding agent to start from business capability, subdomain importance and bounded context before choosing tactical patterns.
It suits business software with enough domain complexity that modeling changes implementation choices, while simple CRUD and generic subsystems stay simple.
What You Get
- A mini rule set with decision rules, trigger rules and a closing checklist for lightweight DDD
- A nano version for tight context budgets and a full version for reference
- A skill description that makes the agent load the rules for subdomain, context map and event tasks
Common Use Cases
- Deciding how much modeling effort a subdomain deserves
- Splitting a model that spreads across billing, identity and fulfillment into separate contexts
- Replacing noisy field-change events with specific past-tense business facts
- Running a short modeling spike or event storming session when workflow terms are unclear
What Makes It Unique
It is the lean DDD option in the repository. It tells the agent to skip full tactical DDD for CRUD and generic subsystems, to invest in the core domain, and to record modeling debt when delivery pressure wins. It also covers integration style choice between RPC, REST and messaging, with the failure semantics of each, which the other DDD sets treat more briefly.
Under The Hood
The skill is a SKILL.md with a name and description, plus Markdown files holding the mini, nano and full versions of the rules. The SKILL.md tells the agent to read the mini file before design or code decisions and the full file only for harder tradeoffs. It contains no scripts. It does not fetch web pages, call APIs, run commands or write files; the agent only reads the rule text.