[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F35B304J07B5XVPMTSP4MY":3,"skill-same:01M7F35B304J07B5XVPMTSP4MY":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7F35B304J07B5XVPMTSP4MY","domain-modeling",null,"For Wheelhouse's build steps: build and sharpen a project's domain model. Use when a step discusses codebase terminology, writes or edits a GLOSSARY.md, or records or edits an ADR.","where-is-brett\u002Fwheelhouse","where-is-brett","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F79561827?v=4","01M7F348PNR9TNC10A1P6A0KMQ","B._.rett","01M7F348Q95CXFA0Q555AYKDZT",0,"MIT","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Fskills\u002Fdomain-modeling\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Fskills\u002Fdomain-modeling\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: domain-modeling\ndescription: \"For Wheelhouse's build steps: build and sharpen a project's domain model. Use when a step discusses codebase terminology, writes or edits a GLOSSARY.md, or records or edits an ADR.\"\n---\n\u003C!-- skills\u002Fdomain-modeling\u002FSKILL.md -->\n\n# Domain Modeling\n\nActively 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.)\n\n## File structure\n\nMost repos have a single context:\n\n```\n\u002F\n├── GLOSSARY.md\n├── docs\u002F\n│   └── adr\u002F\n│       ├── 0001-event-sourced-orders.md\n│       └── 0002-postgres-for-write-model.md\n└── src\u002F\n```\n\nIf a `GLOSSARY-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives:\n\n```\n\u002F\n├── GLOSSARY-MAP.md\n├── docs\u002F\n│   └── adr\u002F                          ← system-wide decisions\n├── src\u002F\n│   ├── ordering\u002F\n│   │   ├── GLOSSARY.md\n│   │   └── docs\u002Fadr\u002F                 ← context-specific decisions\n│   └── billing\u002F\n│       ├── GLOSSARY.md\n│       └── docs\u002Fadr\u002F\n```\n\nCreate 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\u002Fadr\u002F` exists, create it when the first ADR is needed.\n\n## During the session\n\n### Challenge against the glossary\n\nWhen the user uses a term that conflicts with the existing language in `GLOSSARY.md`, call it out immediately. \"Your glossary defines 'cancellation' as X, but you seem to mean Y. Which is it?\"\n\n### Sharpen fuzzy language\n\nWhen the user uses vague or overloaded terms, propose a precise canonical term. \"You're saying 'account': do you mean the Customer or the User? Those are different things.\"\n\n### Discuss concrete scenarios\n\nWhen domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.\n\n### Cross-reference with code\n\nWhen the user states how something works, check whether the code agrees. If you find a contradiction, surface it: \"Your code cancels entire Orders, but you just said partial cancellation is possible. Which is right?\"\n\n### Update GLOSSARY.md inline\n\nWhen a term is resolved, update `GLOSSARY.md` right there. Don't batch these up: capture them as they happen. Use the format in [GLOSSARY-FORMAT.md](.\u002FGLOSSARY-FORMAT.md).\n\n`GLOSSARY.md` should be totally devoid of implementation details. Do not treat `GLOSSARY.md` as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.\n\n### Offer ADRs sparingly\n\nOnly offer to create an ADR when all three are true:\n\n1. **Hard to reverse**: the cost of changing your mind later is meaningful\n2. **Surprising without context**: a future reader will wonder \"why did they do it this way?\"\n3. **The result of a real trade-off**: there were genuine alternatives and you picked one for specific reasons\n\nIf any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](.\u002FADR-FORMAT.md).\n","\u003C!-- skills\u002Fdomain-modeling\u002FSKILL.md -->\n\n# Domain Modeling\n\nActively 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.)\n\n## File structure\n\nMost repos have a single context:\n\n```\n\u002F\n├── GLOSSARY.md\n├── docs\u002F\n│   └── adr\u002F\n│       ├── 0001-event-sourced-orders.md\n│       └── 0002-postgres-for-write-model.md\n└── src\u002F\n```\n\nIf a `GLOSSARY-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives:\n\n```\n\u002F\n├── GLOSSARY-MAP.md\n├── docs\u002F\n│   └── adr\u002F                          ← system-wide decisions\n├── src\u002F\n│   ├── ordering\u002F\n│   │   ├── GLOSSARY.md\n│   │   └── docs\u002Fadr\u002F                 ← context-specific decisions\n│   └── billing\u002F\n│       ├── GLOSSARY.md\n│       └── docs\u002Fadr\u002F\n```\n\nCreate 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\u002Fadr\u002F` exists, create it when the first ADR is needed.\n\n## During the session\n\n### Challenge against the glossary\n\nWhen the user uses a term that conflicts with the existing language in `GLOSSARY.md`, call it out immediately. \"Your glossary defines 'cancellation' as X, but you seem to mean Y. Which is it?\"\n\n### Sharpen fuzzy language\n\nWhen the user uses vague or overloaded terms, propose a precise canonical term. \"You're saying 'account': do you mean the Customer or the User? Those are different things.\"\n\n### Discuss concrete scenarios\n\nWhen domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.\n\n### Cross-reference with code\n\nWhen the user states how something works, check whether the code agrees. If you find a contradiction, surface it: \"Your code cancels entire Orders, but you just said partial cancellation is possible. Which is right?\"\n\n### Update GLOSSARY.md inline\n\nWhen a term is resolved, update `GLOSSARY.md` right there. Don't batch these up: capture them as they happen. Use the format in [GLOSSARY-FORMAT.md](.\u002FGLOSSARY-FORMAT.md).\n\n`GLOSSARY.md` should be totally devoid of implementation details. Do not treat `GLOSSARY.md` as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.\n\n### Offer ADRs sparingly\n\nOnly offer to create an ADR when all three are true:\n\n1. **Hard to reverse**: the cost of changing your mind later is meaningful\n2. **Surprising without context**: a future reader will wonder \"why did they do it this way?\"\n3. **The result of a real trade-off**: there were genuine alternatives and you picked one for specific reasons\n\nIf any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](.\u002FADR-FORMAT.md).\n",{"name":5,"description":7},"main","177d6d482962b196b7c04330246dcb151e315d71","skills\u002Fdomain-modeling","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett","2026-11-15 09:35:39",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add where-is-brett\u002Fwheelhouse --skill domain-modeling",{"tool":37,"command":38},"bunx","bunx skills add where-is-brett\u002Fwheelhouse --skill domain-modeling",{"tool":40,"command":41},"pnpm","pnpm dlx skills add where-is-brett\u002Fwheelhouse --skill domain-modeling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Fskills\u002Fdomain-modeling\u002FSKILL.md",true,[45,51,55,59],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"ADR-FORMAT.md","REFERENCE","参考文档",2779,"https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Fskills\u002Fdomain-modeling\u002FADR-FORMAT.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"GLOSSARY-FORMAT.md",2351,"https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Fskills\u002Fdomain-modeling\u002FGLOSSARY-FORMAT.md",{"path":56,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":16},"LICENSE","许可证",1068,{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"SOURCE.md",1103,"https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Fskills\u002Fdomain-modeling\u002FSOURCE.md",[64,72,79,86,93,100],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":20},"01M7F36VVKJVXMHETFE8RES5MY","shop-design","Lantern Shop's colours, type and shelf-card layout.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finstall\u002Fproject\u002Fdot-claude\u002Fskills\u002Fshop-design\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":20},"01M7F36T3ZFTXE909DQBMHK3Z5","ship-brief","Turns a request into a build brief, opens the pull request and merges it once review passes.","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finstall\u002Fproject\u002Fdot-claude\u002Fskills\u002Fship-brief\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":20},"01M7F36RY5F8TDG3NHE5RC6WBR","reviewing","Lantern Shop's own way of reviewing a change.","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finstall\u002Fproject\u002Fdot-claude\u002Fskills\u002Freviewing\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":20},"01M7F36QKVTNZEDBT1BFCB9SJB","drafting","Drafts a short plan before any work starts.","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finstall\u002Fproject\u002Fdot-claude\u002Fskills\u002Fdrafting\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":20},"01M7F36J8KPVYQAWNEXEDSJJWK","setup","Use when the session start says \"This folder isn't set up for Wheelhouse yet\", that setup is part-way through, that setup's journal couldn't be read, or that Wheelhouse was removed from this folder; and when the Captain asks to set up Wheelhouse, carry on with setup, or remove Wheelhouse from a project.","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Fskills\u002Fsetup\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":20},"01M7F36CG40PHTBG5QP7AZWC9A","review-standards","For Wheelhouse's build steps: review a change against the repository's documented coding standards and a fixed list of code smells.","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Fskills\u002Freview-standards\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Fskills\u002Freview-standards\u002FSKILL.md",[],[]]