Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
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:20260622.889f27e, 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_bvehorsfjivdznbe
GET https://markdownregistry.com/api/v1/resolve?ref=coder/agent-tty/domain-modeling
GET https://markdownregistry.com/api/v1/blob/dfb17ef2da12d6f178a42955fc9880f21d7c7cbf0dede1d15868c521a1ccf0eb
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.
coder/agent-tty · .agents/skills/codebase-design/SKILL.md · Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find…
coder/agent-tty · .agents/skills/diagnosing-bugs/SKILL.md · Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports…
coder/agent-tty · .agents/skills/grill-with-docs/SKILL.md · A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
coder/agent-tty · .agents/skills/grilling/SKILL.md · Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building…
coder/agent-tty · .agents/skills/improve-codebase-architecture/SKILL.md · Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you…
coder/agent-tty · .agents/skills/improve/SKILL.md · Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER…
coder/agent-tty · .agents/skills/release-maintainer/SKILL.md · Internal maintainer SOP for version bumps, release PRs, tagging, publishing, and post-publish verification in this…
coder/agent-tty · .agents/skills/to-issues/SKILL.md · Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet…
coder/agent-tty · .agents/skills/to-prd/SKILL.md · Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of…
coder/agent-tty · .agents/skills/triage/SKILL.md · Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write…
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…
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…
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…
