Skip to content
SkillModel-led108 tokens in use

Domain-Driven Design Distilled

Vaughn Vernon-inspired rules for subdomains, bounded contexts and small aggregates with the least DDD ceremony that works.

3,324 stars on the repository MIT Licenseciembor/agent-rules-books · domain-driven-design-distilled
npx skills add ciembor/agent-rules-books --skill domain-driven-design-distilled
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Domain-Driven Design Distilled costs

33tokens idle
108tokens in use
3,514tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Needs attention
  • Frontmatter11/15
  • Structure0/25
  • Examples0/15
  • Output2/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Fair
  • Development activity44
  • Maintenance72
  • Community52
  • Maturity28
  • Momentum40

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.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers