domain-modeling
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.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- domain-modeling
- description
- 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.
02 资源文件 4
- 参考文档ADR-FORMAT.md3.2 KB
- 参考文档agents/openai.yaml101 B
- 参考文档CREDITS.md2.3 KB
- 参考文档GLOSSARY-FORMAT.md2.2 KB
03 SKILL.md 正文
A prompt or brief naming this skill is its invocation.
Domain Modeling
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 GLOSSARY.md for vocabulary is not this skill: that's a one-line habit any skill can do. This skill is for when you're changing the model, not just consuming it.)
File structure
Most repos have a single context:
/
├── GLOSSARY.md
├── docs/
│ └── adr/
│ ├── 0001-event-sourced-orders.md
│ └── 0002-postgres-for-write-model.md
└── src/
If a GLOSSARY-MAP.md exists at the root, the repo has multiple contexts. The map points to where each one lives:
/
├── GLOSSARY-MAP.md
├── docs/
│ └── adr/ ← system-wide decisions
├── src/
│ ├── ordering/
│ │ ├── GLOSSARY.md
│ │ └── docs/adr/ ← context-specific decisions
│ └── billing/
│ ├── GLOSSARY.md
│ └── docs/adr/
Create files lazily: only when you have something to write. If no GLOSSARY.md exists, create one when the first term is resolved. If no docs/adr/ exists, create it when the first ADR is needed, with the index ADR-FORMAT.md describes when the repo indexes its documentation directories.
Before your first edit to a glossary or ADR, work on a branch of your own in a checkout you own, such as a worktree or fresh clone, never in a shared checkout on the default branch. Each repository whose domain documents change gets its edits delivered as its contribution guide directs, such as one pull request.
During the session
Challenge against the glossary
When the user uses a term that conflicts with the existing language in GLOSSARY.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 GLOSSARY.md inline
When a term is resolved, update GLOSSARY.md right there. Don't batch these up: capture them as they happen. Use the format in GLOSSARY-FORMAT.md.
GLOSSARY.md should be totally devoid of implementation details. Do not treat GLOSSARY.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:
- Hard to reverse: the cost of changing your mind later is meaningful
- Surprising without context: a future reader will wonder "why did they do it this way?"
- 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.
Reads
Paths are relative to the repository root.
GLOSSARY.md, or the rootGLOSSARY-MAP.mdthat points to each context's ownGLOSSARY.md: the domain language. WhenGLOSSARY-MAP.mdis missing, the repository has a single context; when itsGLOSSARY.mdis missing, create it once the first term is resolved.docs/adr/, holdingdocs/adr/<NNNN>-<slug>.mdrecords, and each context's owndocs/adr/: the decisions. When it is missing, create it when the first ADR is needed.<directory>/README.md, such asdocs/adr/README.md: a documentation directory's index. When the repository's documentation directories are missing one, keep no ADR index; when onlydocs/adr/README.mdis missing, create it withdocs/adr/.CONTRIBUTING.md: how the repository delivers glossary and ADR edits, such as one pull request. When it is missing, leave the edits on your own branch.
04 同仓库更多 Skills
repository-standards
In a project with .repo-standards/, read the repository-wide installed rules and report available CLI and standards updates at the start of any work, including work that changes no file. Look up installed rules before changing a file.
author-standards
Create or revise local Repo Standards from confirmed preferences, including accepted checks, fixes, or ordinary-work author skills, or resume unfinished decisions from authoring notes and the current source.
adopt-repository-standards
Use when the user wants to adopt a standards source or adopt, set up, or apply shared repository conventions or standards in a repository.
review
Review project changes against its documented conventions.
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.