domain-modeling is agent-read markdown (skill) from kunolu/640-skills: 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..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns 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/
```
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_n5jrudagpwg6o3y5
GET https://markdownregistry.com/api/v1/resolve?ref=kunolu/640-skills/domain-modeling
GET https://markdownregistry.com/api/v1/blob/327a2b50620e2fd70abc6893cd6965e76b20f8d0adb0dc2c8d5eb3845efb643e
Your agent 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.
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/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…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/diagnosing-bugs/SKILL.md · Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/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.
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/grilling/SKILL.md · Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/handoff/SKILL.md · Compact the current conversation into a handoff document for another agent to pick up.
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/i-have-adhd/SKILL.md · Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/impeccable/SKILL.md · Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/ponytail-audit/SKILL.md · Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/ponytail-debt/SKILL.md · Harvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/ponytail-review/SKILL.md · Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded…
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…
mxyhi/ok-skills · domain-modeling/SKILL.md · Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md…
asymmetric-al/core · .agents/skills/domain-modeling/SKILL.md · Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous…
romiluz13/cc10x · plugins/cc10x/skills/domain-modeling/SKILL.md · Actively build and sharpen a project's domain model — challenge terms against
the glossary, sharpen fuzzy language…
outlinedriven/outline-driven-development · .devin/skills/domain-modeling/SKILL.md · Use when pinning down domain terminology, maintaining the domain model, or when a term conflicts or needs sharpening.
akillness/jeo-skills · .agent-skills/domain-modeling/SKILL.md · Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md…
etr/groundwork · skills/domain-modeling/SKILL.md · Use when designing a product or feature and the project lacks shared, agreed terminology - builds and maintains a pure…
outlinedriven/odin-claude-plugin · plugins/odin-knowledge/skills/domain-modeling/SKILL.md · Use when pinning down domain terminology, maintaining the domain model, or when a term conflicts or needs sharpening.