Skip to content
SkillModel-led98 tokens in use

Domain-Driven Design

Eric Evans-inspired rules for ubiquitous language, bounded contexts, aggregates and a protected core domain.

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

Install command as written in the repository's README

Skill label

measured from its files

What installing Domain-Driven Design costs

29tokens idle
98tokens in use
9,088tokens, 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
  • Size13/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 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.

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