Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rohitg00/domain-modeling
Build the project's shared language and bounded contexts before writing code, so names stay consistent and the agent stops paraphrasing domain concepts. Produces a CONTEXT.md glossary and decision records. Use at the start of a project or feature, or when the codebase and the people describing it speak different languages.
Passed 17 of 21 test cases with the skill, and 14 of 21 without it.
and 2 more in the full report
5 fixed14 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to log a contested decision about whether 'account' should be split into 'BillingAccount' and 'UserIdentity'. Existing files in `docs/decisions/` are `0001-auth.md` and `0002-database.md`. What filename should be used for the new decision record?
| Checked | Without skill | With skill |
|---|---|---|
| Names the file with prefix `0003` inside `docs/decisions/`. | Missed | Passed |
The instructions your model reads when the skill loads.
Most misbuilds start as a language gap: the agent is dropped into a project and left to infer the jargon, so it uses twenty words where the domain has one. A shared language closes the gap. When code, conversation, and the model all draw from the same vocabulary, names line up, navigation gets cheaper, and the model spends fewer tokens reasoning because it has a tighter language to reason in.
CONTEXT.md - the shared-language glossary. One term per line:
term - what it means in this project. Grouped by bounded context when
there is more than one. Point every future session at this file. On re-run,
add new terms and update definitions that changed; do not rewrite the file
wholesale.docs/decisions/NNNN-slug.md for the contested
modeling calls only. Read the directory first and number from the highest
existing record so two records never collide. Skip the obvious ones.test cases passed, vs 14 / 21 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.