[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76PJDKKNB3JWJ6MYKJDEFEP":3,"skill-same:01M76PJDKKNB3JWJ6MYKJDEFEP":78},{"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":37,"commitSha":38,"skillDirectory":39,"forksCount":14,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M76PJDKKNB3JWJ6MYKJDEFEP","domain-modeling",null,"Use when building or sharpening a project's domain model — challenging terminology, writing or editing GLOSSARY.md, or recording an ADR.","jratlee\u002FFDI","jratlee","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F203306824?v=4","01M753581GDCXCM370SDH6W7G7","JRL","01M753582SPQY4E0FZXCF8P3RX",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjratlee\u002FFDI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdomain-modeling\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjratlee\u002FFDI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdomain-modeling\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: domain-modeling\ndescription: Use when building or sharpening a project's domain model — challenging terminology, writing or editing GLOSSARY.md, or recording an ADR.\nversion: 1.0.0\nauthor: Matt Pocock (mattpocock\u002Fskills, MIT); adapted for Hermes\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [domain-modeling, glossary, adr, terminology, design-review]\n    related_skills: [engineering\u002Fgrill-with-docs, productivity\u002Fgrilling]\n---\n\n# Domain Modeling\n\nAdapted from `mattpocock\u002Fskills` -> `skills\u002Fengineering\u002Fdomain-modeling` (MIT).\n\nActively build and sharpen the project's domain model as you design. This is the *active* discipline:\nchallenging terms, inventing edge-case scenarios, and writing the glossary and decisions down the\nmoment they crystallise. (Merely *reading* `GLOSSARY.md` for vocabulary is not this skill: that's a\none-line habit any skill can do. This skill is for when you're changing the model, not just\nconsuming 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\neach 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\nwhen 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\nimmediately. \"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\n'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\nscenarios that probe edge cases and force the user to be precise about the boundaries between\nconcepts.\n\n### Cross-reference with code\n\nWhen the user states how something works, check whether the code agrees. If you find a contradiction,\nsurface it: \"Your code cancels entire Orders, but you just said partial cancellation is possible.\nWhich 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\nhappen. Use the format in [GLOSSARY-FORMAT.md](references\u002FGLOSSARY-FORMAT.md).\n\n`GLOSSARY.md` should be totally devoid of implementation details. Do not treat `GLOSSARY.md` as a\nspec, 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\n   specific reasons\n\nIf any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](references\u002FADR-FORMAT.md).\n\n## Hermes notes\n\n- Read the existing files before writing: `GLOSSARY.md`, `GLOSSARY-MAP.md`, and `docs\u002Fadr\u002F*` are\n  context, and silently contradicting them is worse than not documenting at all.\n- Use `patch`\u002F`write_file` and show the path you changed. Never invent a glossary entry for a term\n  the user has not settled.\n- Outside a repo (Obsidian vault, business docs), keep the same filenames beside the work being\n  planned and state the absolute path in your summary.\n","# Domain Modeling\n\nAdapted from `mattpocock\u002Fskills` -> `skills\u002Fengineering\u002Fdomain-modeling` (MIT).\n\nActively build and sharpen the project's domain model as you design. This is the *active* discipline:\nchallenging terms, inventing edge-case scenarios, and writing the glossary and decisions down the\nmoment they crystallise. (Merely *reading* `GLOSSARY.md` for vocabulary is not this skill: that's a\none-line habit any skill can do. This skill is for when you're changing the model, not just\nconsuming 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\neach 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\nwhen 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\nimmediately. \"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\n'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\nscenarios that probe edge cases and force the user to be precise about the boundaries between\nconcepts.\n\n### Cross-reference with code\n\nWhen the user states how something works, check whether the code agrees. If you find a contradiction,\nsurface it: \"Your code cancels entire Orders, but you just said partial cancellation is possible.\nWhich 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\nhappen. Use the format in [GLOSSARY-FORMAT.md](references\u002FGLOSSARY-FORMAT.md).\n\n`GLOSSARY.md` should be totally devoid of implementation details. Do not treat `GLOSSARY.md` as a\nspec, 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\n   specific reasons\n\nIf any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](references\u002FADR-FORMAT.md).\n\n## Hermes notes\n\n- Read the existing files before writing: `GLOSSARY.md`, `GLOSSARY-MAP.md`, and `docs\u002Fadr\u002F*` are\n  context, and silently contradicting them is worse than not documenting at all.\n- Use `patch`\u002F`write_file` and show the path you changed. Never invent a glossary entry for a term\n  the user has not settled.\n- Outside a repo (Obsidian vault, business docs), keep the same filenames beside the work being\n  planned and state the absolute path in your summary.\n",{"name":5,"author":25,"license":15,"version":26,"metadata":27,"description":7},"Matt Pocock (mattpocock\u002Fskills, MIT); adapted for Hermes","1.0.0",{"hermes":28},{"tags":29,"related_skills":34},[5,30,31,32,33],"glossary","adr","terminology","design-review",[35,36],"engineering\u002Fgrill-with-docs","productivity\u002Fgrilling","main","2e74ca81f4863be77f9e0e61d0ed862b459a80ef",".agents\u002Fskills\u002Fdomain-modeling","https:\u002F\u002Fgithub.com\u002Fjratlee\u002FFDI","https:\u002F\u002Ffalsedawn.industries","https:\u002F\u002Fgithub.com\u002Fjratlee","http:\u002F\u002Fjratlee.com","Forward research.","2026-10-19 22:38:27",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add jratlee\u002FFDI --skill domain-modeling",{"tool":52,"command":53},"bunx","bunx skills add jratlee\u002FFDI --skill domain-modeling",{"tool":55,"command":56},"pnpm","pnpm dlx skills add jratlee\u002FFDI --skill domain-modeling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjratlee\u002FFDI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdomain-modeling\u002FSKILL.md",true,[60,64,70,74],{"path":61,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":16},"LICENSE","许可证",1068,{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"PROVENANCE.md","REFERENCE","参考文档",659,"https:\u002F\u002Fgithub.com\u002Fjratlee\u002FFDI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdomain-modeling\u002FPROVENANCE.md",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002FADR-FORMAT.md",2733,"https:\u002F\u002Fgithub.com\u002Fjratlee\u002FFDI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdomain-modeling\u002Freferences\u002FADR-FORMAT.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002FGLOSSARY-FORMAT.md",2300,"https:\u002F\u002Fgithub.com\u002Fjratlee\u002FFDI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdomain-modeling\u002Freferences\u002FGLOSSARY-FORMAT.md",[79,86,93,100,107,116],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":20},"01M76PTJ6CSGJ8P20GYRBTG763","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002Fjratlee\u002FFDI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvercel-react-native-skills\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":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":20},"01M76PTDRG4DWY93TVRQQWNJVY","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Fjratlee\u002FFDI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvercel-react-best-practices\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":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":20},"01M76PTADCDZZQJG4D28Y56M84","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002Fjratlee\u002FFDI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvercel-composition-patterns\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":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":20},"01M76PSWWJJEC0762TR9YJ7CN6","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002Fjratlee\u002FFDI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":20},"01M76PS6PNXZECWHRPZF3K9513","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjratlee\u002FFDI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fjratlee\u002FFDI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":20},"01M76PKNZ07CRNGVFKY92QMT7E","grilling","Use when the user wants a plan stress-tested.","https:\u002F\u002Fgithub.com\u002Fjratlee\u002FFDI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgrilling\u002FSKILL.md",[],[]]