domain-modeling · rohitg00 — Claude Code skill: shared domain glossary, install
domain-modeling builds the project's shared vocabulary and context boundaries before code gets written, so the agent stops paraphrasing domain terms. Leaves a CONTEXT.md glossary behind.
MIT ★ 2,966 updated 2026-09-29
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflowWhat domain-modeling does
The skill works in four moves. It gathers the nouns and verbs that carry domain meaning from the request, the codebase and the user's own wording. Each one gets a one-line definition written in the project's language rather than a dictionary entry. Where a single word means different things in different parts of the system, the skill names the context and splits the term. Contested modelling calls get a short record: context, decision, rejected options, reason.
You end up with three artifacts. CONTEXT.md holds the glossary, one term - meaning in this project line each, grouped by context when there is more than one. A bounded-context sketch stays short enough to read in fifteen seconds. Decision records go to docs/decisions/NNNN-slug.md, numbered from the highest existing file so two records never collide.
Re-running the skill appends new terms and updates definitions that shifted; it does not rewrite the file from scratch. Renaming the domain to fit your taste is out of scope, and the guardrails say so directly. A glossary that lists everything and never gets updated is worse than having none.
What it helps with
- agree on names before the first line of code
- pull the domain vocabulary into one
CONTEXT.md - split a term that means two different things across services
- record a contested modelling call with the options you rejected
- stop the agent from inventing synonyms for domain concepts
Example prompts for the agent
- Harvest the domain terms for the billing module and split the ones that mean different things in each service.
- Write up the contested order-model decision in
docs/decisions/before we touch code. - Add the new terms from this task to
CONTEXT.mdand fix the definitions that drifted.
How to install domain-modeling
1Plugin marketplace
/plugin marketplace add rohitg00/pro-workflow/plugin install pro-workflow@pro-workflowThis installs the whole pro-workflow plugin with all its skills
2Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill domain-modeling -a claude-code3Manually: put the files in place
~/.claude/skills/domain-modeling/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/domain-modeling/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill domain-modeling -a codex2Manually: put the files in place
.agents/skills/domain-modeling/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill domain-modeling -a cursor2Manually: put the files in place
.cursor/skills/domain-modeling/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rohitg00/pro-workflow skills/domain-modeling2Manually: put the files in place
.github/skills/domain-modeling/SKILL.md1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill domain-modeling -a gemini-cli2Platform CLI
gemini skills install https://github.com/rohitg00/pro-workflow --path skills/domain-modelingManually: put the files in place
.devin/skills/domain-modeling/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about domain-modeling
How do I install domain-modeling in Claude Code?
From the plugin marketplace: run /plugin marketplace add rohitg00/pro-workflow, then /plugin install pro-workflow@pro-workflow.
What does domain-modeling do?
It collects domain terms from the request and the code, pins a short definition on each, and marks where one context ends and another begins. Output is a CONTEXT.md glossary, a context sketch and decision records for the contested calls.
How does it relate to plan-interrogate?
Run it first on a new area; plan-interrogate can call back into it when it hits a term it cannot pin. Both write the same CONTEXT.md, so there is one shared-language file with two entry points.
Source text
SKILL.md · MIT
--- name: domain-modeling description: 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. user-invocable: true --- # 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. 4. **Record the hard calls.** When a modeling choice was contested or will be questioned later, write a short decision record: context, choice, alternatives rejected, why. ## Outputs - **`CONTEXT.md`** - the shared-language glossary. One term per line: `term - what it means in this project`. Grouped by bounded context when there is more than one. Point every future session at this file. On re-run, add new terms and update definitions that changed; do not rewrite the file wholesale. - **Bounded-context sketch** - the contexts and which terms live in each, short enough to read in fifteen seconds. - **Decision records** in `docs/decisions/NNNN-slug.md` for the contested modeling calls only. Read the directory first and number from the highest existing record so two records never collide. Skip the obvious ones. ## Guardrails - The glossary is for the model as much as the human - write it to be loaded, not framed on a wall. - Do not invent terms the project does not use. Reflect the domain; do not rename it. - Keep it small and current. A glossary that lists everything and updates nothing is worse than none. Prune terms that fall out of use. ## Where it fits Run this before `plan-interrogate` on a new area, or let `plan-interrogate` call back here when it hits terms it cannot pin. The `CONTEXT.md` this produces is the same file `plan-interrogate` emits - one shared-language artifact, two ways in.
© Rohit Ghumare · MIT · rohitg00/pro-workflow
Similar skills
All skills for Agent setup: memory, context, orchestration →domain-modeling by other authors comes first.