This skill loads a compact rule set inspired by Vaughn Vernon’s Implementing Domain-Driven Design. It tells a coding agent to name the bounded context first, keep aggregates small and reference other aggregates by identity.
It is the implementation-focused DDD set: repositories per aggregate root, past-tense domain events, thin application services and translation at every context boundary.
What You Get
- A mini rule set with decision rules, trigger rules and a closing checklist for DDD implementation
- A nano version for tight context budgets and a full version for reference
- A skill description that makes the agent load the rules for aggregate, repository and event tasks
Common Use Cases
- Drawing an aggregate boundary and deciding when one transaction may touch several aggregates
- Reshaping a table-shaped repository into aggregate-root access
- Adding an anticorruption layer where a vendor or legacy schema leaks into domain code
- Choosing projections or DTOs when a client needs a shape that differs from the aggregate
What Makes It Unique
It gives the agent an ordered path for generating code: context, language terms, tactical type, a conservative aggregate boundary, identity references, invariants, repositories, services and boundary translations. It also covers event sourcing, with deterministic replay and event versioning, and command and query separation. It is more implementation-focused than the repository’s Distilled set.
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.