Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.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_ `CONTEXT.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:
```
/
├── CONTEXT.md
├── docs/
│ └── adr/
│ ├── 0001-event-sourced-orders.md
│ └── 0002-postgres-for-write-model.md
└── src/
```
If a `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives:
```
/
├── CONTEXT-MAP.md
├── docs/
│ └── adr/ ← system-wide decisions
├── src/
│ ├── ordering/
│ │ ├── CONTEXT.md
│ │ └── docs/adr/ ← context-specific decisions
│ └── billing/
│ ├── CONTEXT.md
│ └── docs/adr/
```
…
The line at the top of this page pins the label git:20260923.15c9348, 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_dalyqk4btd72brtv
GET https://markdownregistry.com/api/v1/resolve?ref=asymmetric-al/core/domain-modeling
GET https://markdownregistry.com/api/v1/blob/703a801331782dbf388908e08e31f00aedd0126c8f1c800174b3728a316488bf
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.
asymmetric-al/core · .agents/skills/accessibility-review/SKILL.md · Audit and fix accessibility in Core UI. Use when changing or reviewing buttons, links, forms, validation, dialogs…
asymmetric-al/core · .agents/skills/agent-browser/SKILL.md · Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages…
asymmetric-al/core · .agents/skills/agent-email-inbox/SKILL.md · Use when building any system where email content triggers actions — AI agent inboxes, automated support handlers…
asymmetric-al/core · .agents/skills/anim/SKILL.md · Tasteful, subtle web UI animation following Emil Kowalski / animations.dev principles. Use when adding or reviewing…
asymmetric-al/core · .agents/skills/animate/SKILL.md · Build an animation from scratch, making the decisions in the order that determines whether it feels right — should it…
asymmetric-al/core · .agents/skills/animation-vocabulary/SKILL.md · Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the…
asymmetric-al/core · .agents/skills/api-design-principles/SKILL.md · Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight…
asymmetric-al/core · .agents/skills/apple-design/SKILL.md · Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing…
asymmetric-al/core · .agents/skills/ask-sonner/SKILL.md · Guide to Sonner, the React toast library — install and wire up the Toaster, pick the right toast() call, promise and…
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…
mathews-tom/armory · skills/domain-modeling/SKILL.md · Use when domain terms or entity relationships are ambiguous, existing definitions conflict with a concrete business…
qshanx/docs-governance · skills/documentation/domain-modeling/SKILL.md · Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md…
