| 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
- 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:
. 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.
