Skip to content
SkillModel-led735 tokens in use

Domain Modeling

Builds and sharpens a project's domain model by challenging terms, stress-testing scenarios and updating GLOSSARY.md and ADRs inline.

328,754 stars on the repository MIT Licensemattpocock/skills · skills/engineering/domain-modeling
claude plugin install mattpocock-skills@claude-plugins-official
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Domain Modeling costs

37tokens idle
735tokens in use
1,907tokens, 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 and code blocks. 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 →
Good
  • Frontmatter12/15
  • Structure17/25
  • Examples9/15
  • Output10/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 →
Excellent
  • Development activity96
  • Maintenance100
  • Community56
  • Maturity32
  • Momentum40

Domain Modeling covers changing a project’s domain language; reading GLOSSARY.md for vocabulary is a one-line habit any skill can do. The skill challenges terms that conflict with the glossary, proposes a canonical term for fuzzy ones, invents edge-case scenarios, checks the code against what you say, and writes each resolved term down immediately.

It also decides when an architecture decision record is worth writing.

What You Get

  • A GLOSSARY.md in a fixed format: bold term, a one or two sentence definition and an Avoid line listing rejected synonyms
  • A GLOSSARY-MAP.md for multi-context repos, listing the contexts and the relationships between them
  • Sequentially numbered ADRs in docs/adr, each as short as one paragraph
  • Contradictions between your statements and the code, raised as questions

Common Use Cases

  • Settling whether account means Customer or User before naming modules
  • Recording why a database or messaging pattern was chosen so that no one reverses it unknowingly
  • Splitting one glossary into per-context glossaries as a system grows

What Makes It Unique

It sets a three-part test for ADRs: the decision is hard to reverse, surprising without context and the result of a real trade-off. If any part is missing, no ADR is offered. It also keeps the glossary free of implementation details and general programming concepts, and creates files only when there is something to write.

Under The Hood

The skill is Markdown with two format guides, GLOSSARY-FORMAT.md and ADR-FORMAT.md. It runs no scripts. During a session the model reads the code, and creates or edits GLOSSARY.md, GLOSSARY-MAP.md and docs/adr files in your repository; those file writes are its only side effect.

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