[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AST3GQVE3V4PYC2PR9BQ8V":3,"skill-same:01M7AST3GQVE3V4PYC2PR9BQ8V":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":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7AST3GQVE3V4PYC2PR9BQ8V","domain-modeling",null,"Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.","Diffusity\u002FrepoSphere_java_backend","Diffusity","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F119410541?v=4","01M7ASS8Z2BQV85KY5WA3C6G5E","Parth Maharaja","01M7ASS8ZRRXZNDAY7F88NBB4N",0,"MIT","https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdomain-modeling\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\r\nname: domain-modeling\r\ndescription: Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.\r\n---\r\n\r\n# Domain Modeling\r\n\r\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.)\r\n\r\n## File structure\r\n\r\nMost repos have a single context:\r\n\r\n```\r\n\u002F\r\n├── CONTEXT.md\r\n├── docs\u002F\r\n│   └── adr\u002F\r\n│       ├── 0001-event-sourced-orders.md\r\n│       └── 0002-postgres-for-write-model.md\r\n└── src\u002F\r\n```\r\n\r\nIf a `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives:\r\n\r\n```\r\n\u002F\r\n├── CONTEXT-MAP.md\r\n├── docs\u002F\r\n│   └── adr\u002F                          ← system-wide decisions\r\n├── src\u002F\r\n│   ├── ordering\u002F\r\n│   │   ├── CONTEXT.md\r\n│   │   └── docs\u002Fadr\u002F                 ← context-specific decisions\r\n│   └── billing\u002F\r\n│       ├── CONTEXT.md\r\n│       └── docs\u002Fadr\u002F\r\n```\r\n\r\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.\r\n\r\n## During the session\r\n\r\n### Challenge against the glossary\r\n\r\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?\"\r\n\r\n### Sharpen fuzzy language\r\n\r\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.\"\r\n\r\n### Discuss concrete scenarios\r\n\r\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.\r\n\r\n### Cross-reference with code\r\n\r\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?\"\r\n\r\n### Update CONTEXT.md inline\r\n\r\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).\r\n\r\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.\r\n\r\n### Offer ADRs sparingly\r\n\r\nOnly offer to create an ADR when all three are true:\r\n\r\n1. **Hard to reverse** — the cost of changing your mind later is meaningful\r\n2. **Surprising without context** — a future reader will wonder \"why did they do it this way?\"\r\n3. **The result of a real trade-off** — there were genuine alternatives and you picked one for specific reasons\r\n\r\nIf any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](.\u002FADR-FORMAT.md).\r\n","# Domain Modeling\r\n\r\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.)\r\n\r\n## File structure\r\n\r\nMost repos have a single context:\r\n\r\n```\r\n\u002F\r\n├── CONTEXT.md\r\n├── docs\u002F\r\n│   └── adr\u002F\r\n│       ├── 0001-event-sourced-orders.md\r\n│       └── 0002-postgres-for-write-model.md\r\n└── src\u002F\r\n```\r\n\r\nIf a `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives:\r\n\r\n```\r\n\u002F\r\n├── CONTEXT-MAP.md\r\n├── docs\u002F\r\n│   └── adr\u002F                          ← system-wide decisions\r\n├── src\u002F\r\n│   ├── ordering\u002F\r\n│   │   ├── CONTEXT.md\r\n│   │   └── docs\u002Fadr\u002F                 ← context-specific decisions\r\n│   └── billing\u002F\r\n│       ├── CONTEXT.md\r\n│       └── docs\u002Fadr\u002F\r\n```\r\n\r\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.\r\n\r\n## During the session\r\n\r\n### Challenge against the glossary\r\n\r\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?\"\r\n\r\n### Sharpen fuzzy language\r\n\r\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.\"\r\n\r\n### Discuss concrete scenarios\r\n\r\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.\r\n\r\n### Cross-reference with code\r\n\r\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?\"\r\n\r\n### Update CONTEXT.md inline\r\n\r\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).\r\n\r\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.\r\n\r\n### Offer ADRs sparingly\r\n\r\nOnly offer to create an ADR when all three are true:\r\n\r\n1. **Hard to reverse** — the cost of changing your mind later is meaningful\r\n2. **Surprising without context** — a future reader will wonder \"why did they do it this way?\"\r\n3. **The result of a real trade-off** — there were genuine alternatives and you picked one for specific reasons\r\n\r\nIf any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](.\u002FADR-FORMAT.md).\r\n",{"name":5,"description":7},"main","7623da0074c7f2756326dd104a40d1b0861a7edf",".agents\u002Fskills\u002Fdomain-modeling","https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend","https:\u002F\u002Fgithub.com\u002FDiffusity","Member @gdg-da | @ossdaiict ","2026-08-18 17:58:04",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Diffusity\u002FrepoSphere_java_backend --skill domain-modeling",{"tool":37,"command":38},"bunx","bunx skills add Diffusity\u002FrepoSphere_java_backend --skill domain-modeling",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Diffusity\u002FrepoSphere_java_backend --skill domain-modeling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdomain-modeling\u002FSKILL.md",true,[45,51,55],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"ADR-FORMAT.md","REFERENCE","参考文档",2813,"https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdomain-modeling\u002FADR-FORMAT.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"agents\u002Fopenai.yaml",104,"https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdomain-modeling\u002Fagents\u002Fopenai.yaml",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"CONTEXT-FORMAT.md",2359,"https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdomain-modeling\u002FCONTEXT-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},"01M7ASXG7ZJ4SX5JDCYSQFWBNG","writing-shape","Writing, exploit — shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-shape\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},"01M7ASXCE1RQCW502FDAJZ7J3X","writing-great-skills","Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.","https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-great-skills\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},"01M7ASXA5NMS4ZEBCTWX29RNZ8","writing-fragments","Writing, explore — mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-fragments\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},"01M7ASX7AM9T3DAJ6A0A6GYTFZ","writing-beats","Writing, exploit — assemble raw material into a journey of beats, grounding each term before a beat leans on it.","https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-beats\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},"01M7ASX2F6FY5EW9SHSV5X2DHC","wizard","Generate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each step, and writing .env files and GitHub Actions secrets.","https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwizard\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},"01M7ASWY2DYFMW5PK6X6YWCC90","wayfinder","Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]