domain-modeling
Installation
SKILL.md
Domain Modeling
Shared language is the cheapest defect prevention there is. This skill keeps two
small artefacts: a GLOSSARY.md where every domain term has one name, one
definition in business language, the synonyms to avoid and an owner who settles
disputes; and a folder of short decision records for choices that are costly to
reverse, surprising later and the result of a real trade-off. Its tools pull
candidate terms out of conversations and code, lint the glossary, find banned
synonyms in docs and identifiers, and keep decision records numbered and linked.
When to use this skill
- The same thing has three names across code, docs, tickets and support macros
- A design conversation keeps stalling on what a word means ("account" — the payer or the login?)
- Starting a GLOSSARY.md for a project or a bounded part of a system
- A decision was just made that a newcomer would otherwise undo
- Onboarding — new people need the vocabulary before the code makes sense
- Before naming a new module, table or API resource, to use the agreed term