This skill loads a compact rule set inspired by Eric Evans’s Domain-Driven Design. It tells a coding agent to keep domain behavior, code, tests and team language aligned inside explicit bounded contexts.
It covers strategic design such as context maps and the core domain, and tactical patterns such as entities, value objects, aggregates, factories and repositories.
What You Get
- A mini rule set with decision rules, trigger rules and a closing checklist for domain modeling
- A nano version for tight context budgets and the full rules as a long reference
- A skill description that makes the agent load the rules for domain, context and aggregate tasks
Common Use Cases
- Moving business decisions out of controllers, SQL and serializers into domain objects
- Choosing a relationship between two contexts, such as an anticorruption layer or customer and supplier
- Renaming code after the team’s understanding of a term changes
- Writing tests that read as examples of the model, including invalid transitions
What Makes It Unique
It is the strategic reference among the repository’s three DDD rule sets. It spends as much effort on context relationships, core domain distillation and large-scale structure as on tactical patterns, and it asks the agent to look for a deeper model when new behavior is hard to explain. The lighter Distilled set and the implementation-focused set cover the same ground at other depths.
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.