[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75TPCVGQ0JS1TVVZDSCECTY":3,"skill-same:01M75TPCVGQ0JS1TVVZDSCECTY":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M75TPCVGQ0JS1TVVZDSCECTY","domain-modeling",null,"Sharpen the project domain model. Use when discussing codebase terminology or editing docs\u002Fglossary.md.","yotamleo-org\u002FHimmel","yotamleo-org","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F344898079?v=4","01M75TKGRE629BDM7G461ABVZP","01M75TKGS2GVCFR1A28MBMK997",15,"MIT","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fmarketplace\u002Fplugins\u002Fdomain-modeling\u002Fskills\u002Fdomain-modeling\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: domain-modeling\ndescription: Sharpen the project domain model. Use when discussing codebase terminology or editing docs\u002Fglossary.md.\n---\n\n> **Vendored, pinned to a commit (HIMMEL-5498).** Source: `mattpocock\u002Fskills`,\n> commit `49dd158d1076134a641b33efb035946536778336`, path\n> `skills\u002Fengineering\u002Fdomain-modeling\u002F` (`SKILL.md`, `GLOSSARY-FORMAT.md`),\n> fetched 2026-10-16. License: MIT, (c) 2026 Matt Pocock (`LICENSE` beside this file).\n> **Deviations from upstream:** (1) output retargeted from a root `GLOSSARY.md` to\n> himmel's `docs\u002Fglossary.md`, in its own table format (one definition per term,\n> an alias points at the canonical term); (2) the multi-context `GLOSSARY-MAP.md`\n> structure and the ADR guidance are dropped (`ADR-FORMAT.md` is not vendored,\n> himmel keeps decision records in the state repo); (3) frontmatter `description`\n> trimmed to match; (4) this header. Re-sync by diffing against the pinned path.\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 down the moment terms crystallise. (Merely *reading* `docs\u002Fglossary.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\nhimmel has a single context: `docs\u002Fglossary.md`. It is the one definition site for the fleet and harness vocabulary; everything else links to it instead of restating a definition. Create no other glossary file.\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 `docs\u002Fglossary.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 docs\u002Fglossary.md inline\n\nWhen a term is resolved, update `docs\u002Fglossary.md` right there. Don't batch these up: capture them as they happen. Use the format in [GLOSSARY-FORMAT.md](.\u002FGLOSSARY-FORMAT.md). Search the glossary for the term and its aliases first: one definition per term, never a second row.\n\n`docs\u002Fglossary.md` should be totally devoid of implementation details. Do not treat it as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.\n","> **Vendored, pinned to a commit (HIMMEL-5498).** Source: `mattpocock\u002Fskills`,\n> commit `49dd158d1076134a641b33efb035946536778336`, path\n> `skills\u002Fengineering\u002Fdomain-modeling\u002F` (`SKILL.md`, `GLOSSARY-FORMAT.md`),\n> fetched 2026-10-16. License: MIT, (c) 2026 Matt Pocock (`LICENSE` beside this file).\n> **Deviations from upstream:** (1) output retargeted from a root `GLOSSARY.md` to\n> himmel's `docs\u002Fglossary.md`, in its own table format (one definition per term,\n> an alias points at the canonical term); (2) the multi-context `GLOSSARY-MAP.md`\n> structure and the ADR guidance are dropped (`ADR-FORMAT.md` is not vendored,\n> himmel keeps decision records in the state repo); (3) frontmatter `description`\n> trimmed to match; (4) this header. Re-sync by diffing against the pinned path.\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 down the moment terms crystallise. (Merely *reading* `docs\u002Fglossary.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\nhimmel has a single context: `docs\u002Fglossary.md`. It is the one definition site for the fleet and harness vocabulary; everything else links to it instead of restating a definition. Create no other glossary file.\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 `docs\u002Fglossary.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 docs\u002Fglossary.md inline\n\nWhen a term is resolved, update `docs\u002Fglossary.md` right there. Don't batch these up: capture them as they happen. Use the format in [GLOSSARY-FORMAT.md](.\u002FGLOSSARY-FORMAT.md). Search the glossary for the term and its aliases first: one definition per term, never a second row.\n\n`docs\u002Fglossary.md` should be totally devoid of implementation details. Do not treat it as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.\n",{"name":5,"description":7},"main","2a00f5c1203047a27ae79f5626e1ae4d34f03c79","marketplace\u002Fplugins\u002Fdomain-modeling\u002Fskills\u002Fdomain-modeling",2,"https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel","https:\u002F\u002Fyotamleo-org.github.io\u002FHimmel\u002F","https:\u002F\u002Fgithub.com\u002Fyotamleo-org","2026-11-15 05:10:30",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add yotamleo-org\u002FHimmel --skill domain-modeling",{"tool":37,"command":38},"bunx","bunx skills add yotamleo-org\u002FHimmel --skill domain-modeling",{"tool":40,"command":41},"pnpm","pnpm dlx skills add yotamleo-org\u002FHimmel --skill domain-modeling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fmarketplace\u002Fplugins\u002Fdomain-modeling\u002Fskills\u002Fdomain-modeling\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"GLOSSARY-FORMAT.md","REFERENCE","参考文档",1807,"https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fmarketplace\u002Fplugins\u002Fdomain-modeling\u002Fskills\u002Fdomain-modeling\u002FGLOSSARY-FORMAT.md",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M75TY3C1HJV3PACB8R2FTAX7","medic","Use inside a Salus medical vault to FILE a medical item into its structured place (skin photo → photo archive + capture note; lesion\u002Fsymptom note; lab\u002FPDF → 00-Sources) and auto-commit, OR to QUERY the vault for a health follow-up (grounded answer + flagged, non-diagnostic morphology read). Triggers on \"file this photo \u002F note \u002F lab\", \"log this into the medical vault\", \"ask the medic\", or any health follow-up while cwd = the medical vault. Organize & surface only — never diagnose (posture-A).","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Ftemplates\u002Fluna-second-brain\u002F_profiles\u002Fsalus\u002F.claude\u002Fskills\u002Fmedic\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M75TY1AV2E5DECQFSGZ01FQ3","stuck-playbook","fixture skill, invoked in the basic transcript fixture","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fscripts\u002Flanes\u002Fbench\u002Fscorecard\u002Ffixtures\u002Ftool-usage\u002Fskills\u002F.claude\u002Fskills\u002Fstuck-playbook\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M75TY05TH00N1KX4H0W1AASQ","never-used-skill","fixture skill, never invoked in any fixture transcript","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fscripts\u002Flanes\u002Fbench\u002Fscorecard\u002Ffixtures\u002Ftool-usage\u002Fskills-config\u002Fskills\u002Fnever-used-skill\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M75TXV4XKHHV36JKHPXK0QAN","used-skill","fixture skill invoked via a Skill tool_use in the fixture transcript","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fscripts\u002Flanes\u002Fbench\u002Fscorecard\u002Ffixtures\u002Fdead-parts\u002Fbasic-repo\u002F.claude\u002Fskills\u002Fused-skill\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M75TXJYNA5BQWC5WWZN4HY95","dead-skill","fixture skill never invoked and never referenced","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fscripts\u002Flanes\u002Fbench\u002Fscorecard\u002Ffixtures\u002Fdead-parts\u002Fbasic-repo\u002F.claude\u002Fskills\u002Fdead-skill\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M75TXAB3RCTMWB02GEKDT17Q","jira-transition","Move\u002Ftransition a Jira issue status (\"move PROJ-46 to In Progress\"). Needs key + target status. Not PR status changes.","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fplugins\u002Fhimmel-jira\u002Fskills\u002Fjira-transition\u002FSKILL.md",[],[]]