domain-modeling
Installation
SKILL.md
Domain Modeling
Purpose
Maintain a shared language between user and agent so both stop translating jargon. A precise glossary makes conversations shorter, code consistently named, and the codebase easier to navigate. This is the active discipline — changing the model. Merely reading a glossary for vocabulary is a habit any skill can have, not this skill.
Use When
- A conversation uses vague, overloaded, or conflicting domain terms.
- Writing or editing a
GLOSSARY.mdat the repo root (followGLOSSARY-MAP.mdif the repo has multiple contexts). - A hard-to-reverse, non-obvious decision was just made and needs an ADR in
docs/adr/.
Avoid When
- General documentation work — use
technical-writing. - Designing a module's interface or shape — use
codebase-design.