domain-modeling
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.
- Installs
- 111
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/rohitg00/pro-workflow --skill domain-modeling- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads domain-modeling automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
- 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.
- 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.
- 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.
- 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.mdfor 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.
FAQ
What does the domain-modeling skill do?
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.
How do I install domain-modeling?
Run npx skills add https://github.com/rohitg00/pro-workflow --skill domain-modeling in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/domain-modeling/ (personal) or .claude/skills/domain-modeling/ (project).
Which AI agents can use domain-modeling?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is domain-modeling safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains domain-modeling?
It is published by rohitg00 in rohitg00/pro-workflow. It has 111 recorded installs.
More from rohitg00/pro-workflow
token-efficiency
rohitg00/pro-workflow
Reduce token waste by 40-60% through anti-sycophancy rules, tool-call budgets, one-pass coding, task profiles, and read-before-write enforcement. Inspired by drona23/claude-token-efficient.
pro-workflow
rohitg00/pro-workflow
Complete AI coding workflow system. Orchestration patterns, 18 hook events, 8 agents, cross-agent support, reference guides, and searchable learnings. Works with Claude Code, Cursor, and 32+ agents.
wrap-up
rohitg00/pro-workflow
End-of-session ritual that audits changes, runs quality checks, captures learnings, and produces a session summary. Use when saying "wrap up", "done for the day", "finish coding", or ending a coding session.
deslop
rohitg00/pro-workflow
Remove AI-generated code slop, unnecessary comments, and over-engineering from the current branch diff. Cleans up boilerplate, simplifies abstractions, strips defensive code, and in skill-file mode lints SKILL.md files for quality. Use when cleaning up code, simplifying, removing boilerplate, before committing, or when reviewing a skill before promoting it.
learn-rule
rohitg00/pro-workflow
Capture a correction or lesson as a persistent learning rule with category, mistake, and correction. Stores, categorises, and retrieves rules for future sessions. Use after mistakes or when the user says "remember this", "don't forget", "note this", or "learn from this".
session-handoff
rohitg00/pro-workflow
Generate a structured handoff document capturing current progress, open tasks, key decisions, and context needed to resume work. Use when ending a session, saying "continue later", "save progress", "session summary", or "pick up where I left off".
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.