Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mattpocock/domain-modeling
Build and sharpen a project's domain model.
Passed 15 of 19 test cases with the skill, and 9 of 19 without it.
and 9 more in the full report
8 fixed10 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have a monorepo containing multiple bounded contexts under src/inventory/ and src/shipping/. There is a CONTEXT-MAP.md at the root. We need to define domain terms for the shipping context. In what file path should the shipping glossary be saved, and where do shipping-specific ADRs belong?
| Checked | Without skill | With skill |
|---|---|---|
| Places the shipping context glossary at src/shipping/CONTEXT.md. | Missed | Passed |
| Places shipping-specific decision records at src/shipping/docs/adr/. | Passed | Passed |
The instructions your model reads when the skill loads.
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.)
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
│ └── docs/adr/
Create files lazily: only when you have something to write. If no GLOSSARY.md exists, create one when the first term is resolved. If no docs/adr/ exists, create it when the first ADR is needed.
test cases passed, vs 9 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.