[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SD31473CM0EFWAH8WEC08":3,"skill-same:01M79SD31473CM0EFWAH8WEC08":59},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M79SD31473CM0EFWAH8WEC08","domain-modeling",null,"Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.","davner\u002Fdotfiles","davner","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F46757810?v=4","01M79SCEJR5ZY0VZD2HJ9HCCXC","Dan Avner","01M79SCEKB7MRS52247SX36BWM",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002F.claude\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 GLOSSARY.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* `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\nWhen `docs\u002Fagents\u002Fdomain.md` names a glossary path or an ADR folder, use those paths in place of the defaults below.\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\n## When headless:\n\nWhen the conversation has said the run is headless, nobody will answer the questions under \"During the session\". Settle a term that conflicts with the glossary, a vague term, or a claim the code contradicts by the confidence rule in `grilling`'s \"When headless:\" section (`~\u002F.claude\u002Fskills\u002Fgrilling\u002FSKILL.md`), and log it to the decision log that section names. Update `GLOSSARY.md` with each settled term as usual. Write an ADR that meets all three tests above without offering it, and log it too.\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\nWhen `docs\u002Fagents\u002Fdomain.md` names a glossary path or an ADR folder, use those paths in place of the defaults below.\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\n## When headless:\n\nWhen the conversation has said the run is headless, nobody will answer the questions under \"During the session\". Settle a term that conflicts with the glossary, a vague term, or a claim the code contradicts by the confidence rule in `grilling`'s \"When headless:\" section (`~\u002F.claude\u002Fskills\u002Fgrilling\u002FSKILL.md`), and log it to the decision log that section names. Update `GLOSSARY.md` with each settled term as usual. Write an ADR that meets all three tests above without offering it, and log it too.\n",{"name":5,"description":7},"main","cc6fb63be1c29cd25ac0547448353eee62f19464","home\u002F.claude\u002Fskills\u002Fdomain-modeling","https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fdavner","www.danavner.com","2026-11-14 18:56:59",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add davner\u002Fdotfiles --skill domain-modeling",{"tool":37,"command":38},"bunx","bunx skills add davner\u002Fdotfiles --skill domain-modeling",{"tool":40,"command":41},"pnpm","pnpm dlx skills add davner\u002Fdotfiles --skill domain-modeling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002F.claude\u002Fskills\u002Fdomain-modeling\u002FSKILL.md",true,[45,51,55],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"ADR-FORMAT.md","REFERENCE","参考文档",2733,"https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002F.claude\u002Fskills\u002Fdomain-modeling\u002FADR-FORMAT.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"agents\u002Fopenai.yaml",101,"https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002F.claude\u002Fskills\u002Fdomain-modeling\u002Fagents\u002Fopenai.yaml",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"GLOSSARY-FORMAT.md",2300,"https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002F.claude\u002Fskills\u002Fdomain-modeling\u002FGLOSSARY-FORMAT.md",[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7DZZNP2P15106XMWHD3CECC","autopilot","Run the new-work flow, idea or board item to reviewed code, with nobody watching.","https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002F.claude\u002Fskills\u002Fautopilot\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M79SEZ2QHSN3YHPP1833ZPPT","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002F.claude\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M79SEW9SFQ2AF5255M2S0PV0","to-tickets","Break a plan, spec, or the current conversation into tracer-bullet tickets grouped into the fewest PRs, each ticket with its blocking edges and first red test, saved as one local file per ticket.","https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002F.claude\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M79SET6W048SZACE3Z3JE0QK","to-spec","Turn the current conversation into a spec saved locally as the reference the agents build from: no interview, just synthesis of what you've already discussed.","https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002F.claude\u002Fskills\u002Fto-spec\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M79SEQTSNJFS3HSCV44FKT9X","teach","Teach the user a new skill or concept, within this workspace.","https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002F.claude\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M79SENJJCBBA37FAHQKZZTS4","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\u002Fdavner\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002F.claude\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]