domain-modeling is agent-read markdown (skill) from chinkan/rustfox: 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.
A 17 of 17 checks passed. Deterministic, no model, same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (3331 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
chinkan/rustfox · 9 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3zs7xm4u2leqo3av
GET https://markdownregistry.com/api/v1/resolve?ref=chinkan/rustfox/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.
chinkan/rustfox · .agents/skills/brainstorming/SKILL.md · You MUST use this before any creative work - creating features, building components, adding functionality, or modifying…
chinkan/rustfox · .agents/skills/cavecrew/SKILL.md · Decision guide for delegating to caveman-style subagents. Tells the main thread WHEN to spawn `cavecrew-investigator`…
chinkan/rustfox · .agents/skills/caveman-compress/SKILL.md · Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens…
chinkan/rustfox · .agents/skills/caveman-help/SKILL.md · Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger…
chinkan/rustfox · .agents/skills/caveman-review/SKILL.md · Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment…
chinkan/rustfox · .agents/skills/caveman-stats/SKILL.md · Show real token usage and estimated savings for the current session. Reads directly from the Claude Code session log —…
chinkan/rustfox · .agents/skills/caveman/SKILL.md · Ultra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full…
chinkan/rustfox · .agents/skills/code-review/SKILL.md · Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code…
chinkan/rustfox · .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…
chinkan/rustfox · .agents/skills/design-an-interface/SKILL.md · Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to…
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.
