skills sourced live from GitHub · all skills listed are free · each skill is provided under its author's license.
home / Coding / Domain Modeling Skill by @mattpocock
The skill is the skills/engineering/domain-modeling folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.
Build and sharpen a project's domain model.
Helps you build and sharpen a project's domain model. It challenges your terminology against a glossary, tightens fuzzy language, tests ideas against concrete scenarios, cross-references the code and records decisions as ADRs.
The original SKILL.md is organised into these sections:
Written and maintained by @mattpocock. It is published under the MIT license, which allows reuse with attribution. See the author profile. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.
# Domain Modeling Actively build and sharpen the project's domain model as you design. This is the *active* discipline: challenging terms, inventing edge-case scenarios, and writing the glossary and decisions down the moment they crystallise. (Merely *reading* `GLOSSARY.md` for vocabulary is not this skill: that's a one-line habit any skill can do. This skill is for when you're changing the model, not just consuming it.) ## File structure Most repos have a single context: ``` / ├── GLOSSARY.md ├── docs/ │ └── adr/ │ ├── 0001-event-sourced-orders.md │ └── 0002-postgres-for-write-model.md └── src/ ``` If a `GLOSSARY-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives: ``` / ├── GLOSSARY-MAP.md ├── docs/ │ └── adr/ ← system-wide decisions ├── src/ │ ├── ordering/ │ │ ├── GLOSSARY.md │ │ └── docs/adr/ ← context-specific decisions │ └── billing/ │ ├── GLOSSARY.md …
Excerpt only, quoted from the author's repository. Open the repository for the complete file.