Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Domain Modeling
Actively build and sharpen the project's domain model as you design. This is the *active* discipline: challenging terms, inventing edge-case scenarios, and writing the glossary and decisions down the moment they crystallise. (Merely *reading* `GLOSSARY.md` for vocabulary is not this skill: that's a one-line habit any skill can do. This skill is for when you're changing the model, not just consuming it.)
## File structure
Most repos have a single context:
```
/
├── GLOSSARY.md
├── docs/
│ └── adr/
│ ├── 0001-event-sourced-orders.md
│ └── 0002-postgres-for-write-model.md
└── src/
```
If a `GLOSSARY-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives:
```
/
├── GLOSSARY-MAP.md
├── docs/
│ └── adr/ ← system-wide decisions
├── src/
│ ├── ordering/
│ │ ├── GLOSSARY.md
│ │ └── docs/adr/ ← context-specific decisions
│ └── billing/
│ ├── GLOSSARY.md
│ └── docs/adr/
```
…
The line at the top of this page pins the label git:20261006.f349c21, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_wbfnyhfsta5izogw
GET https://markdownregistry.com/api/v1/resolve?ref=kunanonj/ai-skills-hub/domain-modeling
GET https://markdownregistry.com/api/v1/blob/3fe021ee257d772847160d6a4e4a87cabc47529b5b3920957144797f1cef7f65
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
kunanonj/ai-skills-hub · plugins/superstacks/skills/code-review/SKILL.md · Use when reviewing a branch, PR, or WIP since a commit, tag, or merge-base. Two-axis Standards and Spec review via…
kunanonj/ai-skills-hub · plugins/superstacks/skills/diagnosing-bugs/SKILL.md · Use when the user says diagnose or debug this, or reports something broken, throwing, failing, or slow.
kunanonj/ai-skills-hub · plugins/superstacks/skills/gardening/SKILL.md · Use when finding small maintenance work. One concern per PR, each with a verify command and a small diff budget.
kunanonj/ai-skills-hub · plugins/superstacks/skills/grill-with-docs/SKILL.md · Use when grilling a plan or design that should also produce ADRs and a glossary as you go.
kunanonj/ai-skills-hub · plugins/superstacks/skills/grilling/SKILL.md · Use when the user wants to stress-test a plan, decision, or idea, or uses any grill trigger phrases.
kunanonj/ai-skills-hub · plugins/superstacks/skills/how/SKILL.md · Use for how-does-X-work walkthroughs, placement, ownership, and layering questions before changing code.
kunanonj/ai-skills-hub · plugins/superstacks/skills/intake-triage/SKILL.md · Use when a coordinator has a batch of bug reports, feedback, or alerts. Deduplicate, group, score two-way vs one-way…
kunanonj/ai-skills-hub · plugins/superstacks/skills/interrogate/SKILL.md · Use for interrogate, adversarial review, multi-model review, challenge this, stress test this code, or find blind spots.
kunanonj/ai-skills-hub · plugins/superstacks/skills/mistake-to-constraint/SKILL.md · Use when a mistake repeats. Encode it as the strongest guard — type or runtime, lint, test, directory convention, then…
kunanonj/ai-skills-hub · plugins/superstacks/skills/sample-review/SKILL.md · Use when sampling recently merged PRs against repo standards and CONSTRAINTS.md. Propose environment tightenings, not…
rohitg00/pro-workflow · skills/domain-modeling/SKILL.md · Build the project's shared language and bounded contexts before writing code, so names stay consistent and the agent…
borghei/claude-skills · engineering/domain-modeling/SKILL.md · Keep a project glossary of domain terms and lightweight decision records, and catch banned synonyms in docs and code…
rsmdt/the-startup · plugins/team/skills/development/domain-modeling/SKILL.md · Unified domain and data modeling for business entities, invariants, schema design, aggregate boundaries, and evolution…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/domain-modeling/SKILL.md · Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md…
mxyhi/ok-skills · domain-modeling/SKILL.md · Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md…
asymmetric-al/core · .agents/skills/domain-modeling/SKILL.md · Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md…
mathews-tom/armory · skills/domain-modeling/SKILL.md · Use when domain terms or entity relationships are ambiguous, existing definitions conflict with a concrete business…