Skip to main content
skill CX Codex

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

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflow
Open on GitHub

What 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.md and fix the definitions that drifted.

How to install domain-modeling

1Plugin marketplace

/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflow

This installs the whole pro-workflow plugin with all its skills

2Skills CLI (Vercel)

npx skills add rohitg00/pro-workflow --skill domain-modeling -a claude-code

3Manually: put the files in place

~/.claude/skills/domain-modeling/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/domain-modeling/

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.

domain-modeling Matt Pocock The domain-modeling skill sharpens project terminology, maintains GLOSSARY.md, and records selected architecture decisions in ADRs. Use it while the domain model is changing. CX Codex +1 876,391installs domain-modeling Rudolf S. The domain-modeling skill turns business rules into domain models, aggregate boundaries, and storage decisions. Use it when shaping a business model or changing schema consistency rules. CX Codex +1 ★ 587repo stars dotnet-domain-modeling wshaddix dotnet-domain-modeling guides pure C# Domain-Driven Design modeling with entities, aggregate roots, value objects, and domain events, keeping business logic isolated from ORM concerns. CX Codex +1 539installs establishing-project-context GanyuanRan establishing-project-context keeps domain terms in CONTEXT.md so people and agents call the same things by the same names. Useful when a term gets renamed, deprecated or overloaded. CX Codex +1 ★ 1,450repo stars glossary aspi6246 A per-project dictionary in GLOSSARY.md covering definitions, abbreviations and command phrases the agent carries out on a single word. CX Codex +1 ★ 165repo stars drydock Yeachan-Heo drydock — a skill for Claude Code, Codex, Cursor, Copilot, and Gemini CLI that sets up a shared repo harness on first run. It seeds CLAUDE.md and GLOSSARY.md immediately; every other surface appears on first use. CX Codex +1 273installs domain-model sammcj Skill to actively shape your domain model: challenges terms against the glossary, stress-tests boundaries with scenarios, records glossary and decisions in CONTEXT.md and ADRs. CX Codex +1 ★ 173repo stars domain-analysis tech-leads-club domain-analysis walks a codebase to find subdomains and suggest where service boundaries belong. Useful before splitting a monolith. CX Codex +1 381installs

From the same set83

The whole set →
compact-guard compact-guard is a Claude Code skill that records task state before context compaction and helps restore it afterward. Run it before /compact or when an auto-compaction warning appears. CX Codex +1 ★ 2,966repo stars handoff Generates a structured handoff document for passing work to another Claude session or your future self. Records status, decisions, learnings, and a resume point. CX Codex +1 ★ 2,966repo stars replay replay finds relevant past learnings and mistakes in a local SQLite database before starting a task. Surfaces project context to reduce repeated edits. CX Codex +1 ★ 2,966repo stars insights The insights skill turns project memory and session history into analytics on corrections, saved learnings, and coding activity. Ask for a report to spot recurring patterns. CX Codex +1 ★ 2,966repo stars llm-gate llm-gate configures prompt and agent hooks in Claude Code to validate commit messages, stop dangerous terminal commands, and catch secret leaks before execution. CX Codex +1 ★ 2,966repo stars cost-tracker The cost-tracker skill helps you review Claude Code session costs, set budget checkpoints, and spot expensive work patterns. Use it when planning work across sessions. CX Codex +1 ★ 2,966repo stars reviewer reviewer — a subagent that reviews code line by line, reading actual files and citing every finding with exact quotes. Use before committing, during PR review, or after major changes. CX Codex ★ 2,966repo stars skill-conventions skill-conventions defines standards for workflow skills: separates human invocation from auto-triggers, governs state writes, and keeps the skill router in sync. CX Codex +1 ★ 2,966repo stars

Project sponsors

Companies that keep this analytics open