[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C2YQ4FSRCPWAGM8K8SBV69":3,"skill-same:01M7C2YQ4FSRCPWAGM8K8SBV69":58},{"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":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7C2YQ4FSRCPWAGM8K8SBV69","domain-modeling",null,"Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.","PhmnPh\u002Fclaude-config","PhmnPh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206572176?v=4","01M7C2Y3QW8QEWQYD46EM0WMSV","01M7C2Y3RG0T6ZRNN1QWMMVMXQ",0,"MIT","https:\u002F\u002Fgithub.com\u002FPhmnPh\u002Fclaude-config\u002Fblob\u002Fmain\u002Fclaude\u002Fskills\u002Fdomain-modeling\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FPhmnPh\u002Fclaude-config\u002Fblob\u002Fmain\u002Fclaude\u002Fskills\u002Fdomain-modeling\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: domain-modeling\ndescription: Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.\n---\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* `CONTEXT.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├── CONTEXT.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 `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives:\n\n```\n\u002F\n├── CONTEXT-MAP.md\n├── docs\u002F\n│   └── adr\u002F                          ← system-wide decisions\n├── src\u002F\n│   ├── ordering\u002F\n│   │   ├── CONTEXT.md\n│   │   └── docs\u002Fadr\u002F                 ← context-specific decisions\n│   └── billing\u002F\n│       ├── CONTEXT.md\n│       └── docs\u002Fadr\u002F\n```\n\nCreate files lazily: only when you have something to write. If no `CONTEXT.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 `CONTEXT.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 CONTEXT.md inline\n\nWhen a term is resolved, update `CONTEXT.md` right there. Don't batch these up: capture them as they happen. Use the format in [CONTEXT-FORMAT.md](.\u002FCONTEXT-FORMAT.md).\n\n`CONTEXT.md` should be totally devoid of implementation details. Do not treat `CONTEXT.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","# 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* `CONTEXT.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├── CONTEXT.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 `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives:\n\n```\n\u002F\n├── CONTEXT-MAP.md\n├── docs\u002F\n│   └── adr\u002F                          ← system-wide decisions\n├── src\u002F\n│   ├── ordering\u002F\n│   │   ├── CONTEXT.md\n│   │   └── docs\u002Fadr\u002F                 ← context-specific decisions\n│   └── billing\u002F\n│       ├── CONTEXT.md\n│       └── docs\u002Fadr\u002F\n```\n\nCreate files lazily: only when you have something to write. If no `CONTEXT.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 `CONTEXT.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 CONTEXT.md inline\n\nWhen a term is resolved, update `CONTEXT.md` right there. Don't batch these up: capture them as they happen. Use the format in [CONTEXT-FORMAT.md](.\u002FCONTEXT-FORMAT.md).\n\n`CONTEXT.md` should be totally devoid of implementation details. Do not treat `CONTEXT.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","2e487cdaeb989b9f77052c38e05a9a32a21d9f12","claude\u002Fskills\u002Fdomain-modeling","https:\u002F\u002Fgithub.com\u002FPhmnPh\u002Fclaude-config","https:\u002F\u002Fgithub.com\u002FPhmnPh","2026-09-16 22:26:04",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add PhmnPh\u002Fclaude-config --skill domain-modeling",{"tool":36,"command":37},"bunx","bunx skills add PhmnPh\u002Fclaude-config --skill domain-modeling",{"tool":39,"command":40},"pnpm","pnpm dlx skills add PhmnPh\u002Fclaude-config --skill domain-modeling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPhmnPh\u002Fclaude-config\u002Fblob\u002Fmain\u002Fclaude\u002Fskills\u002Fdomain-modeling\u002FSKILL.md",true,[44,50,54],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"ADR-FORMAT.md","REFERENCE","参考文档",2733,"https:\u002F\u002Fgithub.com\u002FPhmnPh\u002Fclaude-config\u002Fblob\u002Fmain\u002Fclaude\u002Fskills\u002Fdomain-modeling\u002FADR-FORMAT.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"CONTEXT-FORMAT.md",2290,"https:\u002F\u002Fgithub.com\u002FPhmnPh\u002Fclaude-config\u002Fblob\u002Fmain\u002Fclaude\u002Fskills\u002Fdomain-modeling\u002FCONTEXT-FORMAT.md",{"path":55,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":15},"LICENSE","许可证",1068,[59,67,75,83,91,99],{"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":63,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7C33F4HEPNCDR2RNG62YZX4","wayfinder","Map unresolved decisions for a large initiative and work through their dependencies until a plan is actionable.","https:\u002F\u002Fgithub.com\u002FPhmnPh\u002Fclaude-config\u002Fblob\u002Fmain\u002Fcodex\u002Fskills\u002Fwayfinder\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FPhmnPh\u002Fclaude-config\u002Fblob\u002Fmain\u002Fcodex\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":71,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7C338XN7376BKCGTKFBQ583","to-tickets","Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).","https:\u002F\u002Fgithub.com\u002FPhmnPh\u002Fclaude-config\u002Fblob\u002Fmain\u002Fcodex\u002Fskills\u002Fto-tickets\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FPhmnPh\u002Fclaude-config\u002Fblob\u002Fmain\u002Fcodex\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7C336B4KYZGGMKPNKEFPV00","to-spec","Turn an agreed feature or plan into a proportionate, testable specification at the requested destination.","https:\u002F\u002Fgithub.com\u002FPhmnPh\u002Fclaude-config\u002Fblob\u002Fmain\u002Fcodex\u002Fskills\u002Fto-spec\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FPhmnPh\u002Fclaude-config\u002Fblob\u002Fmain\u002Fcodex\u002Fskills\u002Fto-spec\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7C32Y5F6M2SQ675YK6679E9","tdd","Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","https:\u002F\u002Fgithub.com\u002FPhmnPh\u002Fclaude-config\u002Fblob\u002Fmain\u002Fcodex\u002Fskills\u002Ftdd\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FPhmnPh\u002Fclaude-config\u002Fblob\u002Fmain\u002Fcodex\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7C32TNN391FBBA7NQHDX3MQ","setup-matt-pocock-skills","Configure missing tracker and domain-document conventions for the Matt Pocock workflows in a repository.","https:\u002F\u002Fgithub.com\u002FPhmnPh\u002Fclaude-config\u002Fblob\u002Fmain\u002Fcodex\u002Fskills\u002Fsetup-matt-pocock-skills\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FPhmnPh\u002Fclaude-config\u002Fblob\u002Fmain\u002Fcodex\u002Fskills\u002Fsetup-matt-pocock-skills\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7C32R800TF424Y0SHWGR9BB","research","Investigate a specific technical question using primary sources and save a cited research note.","https:\u002F\u002Fgithub.com\u002FPhmnPh\u002Fclaude-config\u002Fblob\u002Fmain\u002Fcodex\u002Fskills\u002Fresearch\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FPhmnPh\u002Fclaude-config\u002Fblob\u002Fmain\u002Fcodex\u002Fskills\u002Fresearch\u002FSKILL.md",[],[]]