Domain Modeling

The active discipline of shaping the model — challenging terms, inventing edge-case scenarios, and writing vocabulary down the moment it crystallizes. Merely reading a glossary for vocabulary is a one-line habit any skill does; this skill is for when you're changing the model, not consuming it.

Artifact

Maintain the project's glossary in its existing convention. If there is none, create CONTEXT.md at the repo root. Record decisions that settle a term via /create-adr so the why is preserved separately from the what.

Ubiquitous language

One term, one meaning, used everywhere — prose, code, docs, and the glossary agree. For each term write:

• A crisp definition.
• An Avoid list of the rejected synonyms, so the same concept never travels under two names.

When the same word means two things, that ambiguity is the work — split it into two named terms and retire the overloaded one.

Sharpen by stress