domain-modeling is agent-read markdown (skill) from rohitg00/pro-workflow: Build the project's shared language and bounded contexts before writing code, so names stay consistent and the agent stops paraphrasing domain concepts. Produces a CONTEXT.md glossary and decision records. Use at the start of a project or feature, or when the codebase and the people describing it speak different languages..
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
Most misbuilds start as a language gap: the agent is dropped into a project
and left to infer the jargon, so it uses twenty words where the domain has
one. A shared language closes the gap. When code, conversation, and the model
all draw from the same vocabulary, names line up, navigation gets cheaper, and
the model spends fewer tokens reasoning because it has a tighter language to
reason in.
## Method
1. **Harvest the terms.** From the request, the codebase, and the user's own
words, list the nouns and verbs that carry domain meaning - the concepts a
newcomer would have to ask about. Prefer the user's word over a synonym you
like better.
2. **Pin each one.** Write a one-line definition in the project's own language,
not a dictionary definition. If two terms blur together, force the
distinction or collapse them - ambiguity here becomes inconsistent names in
code.
3. **Draw the boundaries.** Where the same word means different things in
different parts of the system, that is a boundary. Name each context and
note which terms belong to it. A term that means two things is two terms.
…
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_2zvp5rc6npjryqky
GET https://markdownregistry.com/api/v1/resolve?ref=rohitg00/pro-workflow/domain-modeling
GET https://markdownregistry.com/api/v1/blob/0e9ba07d6d34b1ee05ac40072e345a1d7abc7e00d9778db98e025bee8db37eb1
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.
rohitg00/pro-workflow · skills/agent-teams/SKILL.md · Coordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and…
rohitg00/pro-workflow · skills/auto-setup/SKILL.md · Auto-configure quality gates, hooks, and settings for a new project. Detects project type and sets up appropriate…
rohitg00/pro-workflow · skills/batch-orchestration/SKILL.md · Decompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for…
rohitg00/pro-workflow · skills/bug-capture/SKILL.md · Capture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the…
rohitg00/pro-workflow · skills/compact-guard/SKILL.md · Smart context compaction with state preservation. Saves critical files, task progress, and working state before…
rohitg00/pro-workflow · skills/context-optimizer/SKILL.md · Optimize token usage and context management. Use when sessions feel slow, context is degraded, or you're running out of…
rohitg00/pro-workflow · skills/cost-tracker/SKILL.md · Track session costs, set budget alerts, and optimize token spend. Use to check costs mid-session or set spending limits.
rohitg00/pro-workflow · skills/design-engineering/SKILL.md · Apply interface craft when building or reviewing UI - motion, easing, timing, springs, component feel, and visual…
rohitg00/pro-workflow · skills/deslop/SKILL.md · Remove AI-generated code slop, unnecessary comments, and over-engineering from the current branch diff. Cleans up…
rohitg00/pro-workflow · skills/improve-architecture/SKILL.md · Audit an area of the codebase and propose the smallest structural moves that improve it - untangle boundaries, kill…
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…
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 CONTEXT.md…
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.
