Domain modeling
Clarifies a project’s domain terms and boundaries and records the decisions in a glossary or architecture decision record.
When to use it
- People use different words for the same thing, or one word for two things.
- System boundaries are unclear before a larger change.
- You want a GLOSSARY.md or an ADR written down.
A practical example
You ask
“We keep mixing up accounts, workspaces and organisations. Sort out the terms.”
Your agent does
It maps how each term is used in code and conversation, proposes definitions and records them in a glossary.
What gets installed
A single instruction file, SKILL.md, which the agent reads when the skill applies.
- SKILL.md3,772 bytes
Credit and license
Written independently, inspired by the domain-modeling skill in Matt Pocock’s skills collection; no source text was copied.