domain-model — Claude Code skill: refine your domain model
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.
Apache-2.0 ★ 173 updated 2026-10-24
npx skills add sammcj/agentic-coding --skill domain-model -a claude-codeWhat domain-model does
This skill moves domain modelling forward as you design. It does not passively read CONTEXT.md — it challenges terms, spots contradictions between what you say and what the code does, invents edge-case scenarios. When a term crystallises, it records it in the glossary immediately. When a decision is hard to reverse, unexpected without context, and the result of trade-offs, it writes an ADR.
File layout depends on scope. Single context: CONTEXT.md at the root, docs/adr/ nearby. Multiple contexts: CONTEXT-MAP.md at the root points to each one. Files are created on demand — first term resolved means CONTEXT.md exists, first ADR needed means docs/adr/ exists.
The skill works within the session: calls you out if a new term conflicts with the glossary, proposes precise language over vague words, tests an example against the code. CONTEXT.md stays a pure glossary with no implementation details.
What it helps with
- catch fuzzy and overloaded terminology before it spreads through the codebase
- keep the glossary in sync with code as the model evolves
- capture architectural decisions the moment they solidify
- probe model boundaries with specific scenarios
- hold CONTEXT.md in mind and cross-check against it
Example prompts for the agent
- Help me pin down the terms: what's the difference between a cancellation and a refund in our model?
- My code allows partial order cancellation, but I said earlier that only full cancellation is possible. Give me scenarios where this breaks.
- Update CONTEXT.md: I've decided Account is not Customer — it's User, because one Account can belong to multiple Users.
How to install domain-model
1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill domain-model -a claude-code2Manually: put the files in place
~/.claude/skills/domain-model/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/domain-model/
1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill domain-model -a codex2Manually: put the files in place
.agents/skills/domain-model/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill domain-model -a cursor2Manually: put the files in place
.cursor/skills/domain-model/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sammcj/agentic-coding Skills_disabled/domain-model/SKILL.md2Manually: put the files in place
.github/skills/domain-model/SKILL.md1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill domain-model -a gemini-cli2Platform CLI
gemini skills install https://github.com/sammcj/agentic-coding --path Skills_disabled/domain-modelManually: put the files in place
.devin/skills/domain-model/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-model
How do I install domain-model in Claude Code?
Run npx skills add sammcj/agentic-coding --skill domain-model -a claude-code, then open ~/.claude/skills/domain-model/SKILL.md.
What's the difference between this skill and just reading CONTEXT.md?
This skill actively challenges your assumptions, spots contradictions in the code, invents boundary scenarios, and records decisions as they crystallise. Reading CONTEXT.md is passive work any skill can do in a line.
When should I write an ADR?
Only when all three hold: the decision is hard to reverse, its reasoning will puzzle a future reader, and there were genuine alternatives. If any one is missing, skip it.
Source text
SKILL.md · Apache-2.0
--- name: domain-model description: Actively build and sharpen a project's domain model - challenge terms against the glossary, stress-test boundaries with scenarios, cross-reference against the code, and record the glossary (CONTEXT.md) and decisions (ADRs) the moment they crystallise. Use when you are changing the domain model itself, pinning down a ubiquitous language, or recording an architectural decision. disable-model-invocation: true metadata: source: https://github.com/mattpocock/skills --- # Domain modelling 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 is a one-line habit any skill can do. This skill is for when you are 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/ ``` Create files lazily - only when you have something to write. If no `CONTEXT.md` exists, create one when the first term is resolved. If no `docs/adr/` exists, create it when the first ADR is needed. ## During the session ### Challenge against the glossary When the user uses a term that conflicts with the existing language in `CONTEXT.md`, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y - which is it?" ### Sharpen fuzzy language When the user uses vague or overloaded terms, propose a precise canonical term. "You're saying 'account' - do you mean the Customer or the User? Those are different things." ### Discuss concrete scenarios When domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts. ### Cross-reference with code When the user states how something works, check whether the code agrees. If you find a contradiction, surface it: "Your code cancels entire Orders, but you just said partial cancellation is possible - which is right?" ### Update CONTEXT.md inline When a term is resolved, update `CONTEXT.md` right there. Don't batch these up - capture them as they happen. Use the format in [CONTEXT-FORMAT.md](./CONTEXT-FORMAT.md). `CONTEXT.md` should be totally devoid of implementation details. Do not treat `CONTEXT.md` as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else. ### Offer ADRs sparingly Only offer to create an ADR when all three are true: 1. **Hard to reverse** - the cost of changing your mind later is meaningful 2. **Surprising without context** - a future reader will wonder "why did they do it this way?" 3. **The result of a real trade-off** - there were genuine alternatives and you picked one for specific reasons If any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](./ADR-FORMAT.md).
© sammcj · Apache-2.0 · sammcj/agentic-coding