Domain Modeling
Sharpens your project's domain model live — challenging fuzzy terms and writing the glossary and ADRs as decisions crystallise
- What
- Sharpens your project's domain model live — challenging fuzzy terms and writing the glossary and ADRs as decisions crystallise
- Cost
- Free
- Needs
- a Muse account with skill installation enabled
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a domain-modeling skill for the active discipline of building a project's shared language, not just reading it. It challenges terms against the glossary the moment they conflict ("your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?"), sharpens fuzzy language into canonical terms, stress-tests relationships with invented edge-case scenarios, and cross-references what you say against what the code actually does. Resolved terms are written to CONTEXT.md inline — never batched — kept strictly a glossary with zero implementation details; hard-to-reverse, surprising, genuinely-traded-off decisions become ADRs, and only those. It handles multi-context repos via a CONTEXT-MAP.md pointing at per-area glossaries. By @mattpocock, listed here with credit to its creator. Honest caveats: it edits your CONTEXT.md and docs/adr/ as the session goes, so it writes into your repo by design — review the diffs; it creates files lazily, which means a first session can scatter new files at the root until the structure settles. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Muse account with skill installation enabled Install "Domain Modeling" for me. Sharpens your project's domain model live — challenging fuzzy terms and writing the glossary and ADRs as decisions crystallise Repository: https://github.com/mattpocock/skills/blob/main/skills/engineering/domain-modeling/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "mattpocock-domain-modeling". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.