[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M788FEWGMMZH6PV3BWM2ENN1":3,"skill-same:01M788FEWGMMZH6PV3BWM2ENN1":54},{"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":5,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M788FEWGMMZH6PV3BWM2ENN1","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.","evist0\u002Fokf-matt-skills","evist0","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F32814970?v=4","01M788F6GHSVY6BVJ2HC65ECWV","Danil Tankov","01M788F6HD2SSXYGAAC67YD47C",18,"MIT","https:\u002F\u002Fgithub.com\u002Fevist0\u002Fokf-matt-skills\u002Fblob\u002Fmain\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 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.\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* the knowledge bundle's glossary 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\nThe domain model lives in an **Open Knowledge Format (OKF)** knowledge bundle at `knowledge\u002F` in the repo root. Most repos have a single context:\n\n```\nknowledge\u002F\n├── index.md              ← bundle map (reserved: no frontmatter)\n├── log.md                ← change history, newest first (reserved: no frontmatter)\n├── glossary\u002F             ← one file per term (the glossary)\n│   ├── index.md\n│   ├── order.md\n│   └── customer.md\n└── adr\u002F                  ← one file per decision\n    ├── index.md\n    ├── adr-0001-event-sourced-orders.md\n    └── adr-0002-postgres-for-write-model.md\n```\n\nFor multiple bounded contexts, each context is a subdirectory inside the one bundle (`knowledge\u002Fordering\u002Fglossary\u002F`, `knowledge\u002Fbilling\u002Fglossary\u002F`, …) and `knowledge\u002Findex.md` is the context map. See [CONTEXT-FORMAT.md](.\u002FCONTEXT-FORMAT.md).\n\nCreate files lazily — only when you have something to write. If no `knowledge\u002Fglossary\u002F` exists, create it when the first term is resolved. If no `knowledge\u002Fadr\u002F` exists, create it when the first ADR is needed. Whenever knowledge changes, update the concept AND append to `knowledge\u002Flog.md`.\n\n### Extending the bundle (new concept categories)\n\n`glossary\u002F` and `adr\u002F` are the two categories every bundle has; `spec\u002F` (written by `\u002Fto-spec`) is the third canonical one. But OKF is an **open** format — `type` is a free field and the bundle is not limited to a fixed set of folders. When you meet a durable domain entity that genuinely fits none of them — a recurring *kind* of thing the project needs recorded in its own right — a new concept category is legitimate.\n\nDon't spin one up silently. When you judge a new category is warranted:\n\n1. **Propose it** — name the category, say what kind of entity it holds and why glossary\u002Fadr\u002Fprd don't fit.\n2. **Get the user's sanction** before creating the directory.\n3. **Register it** in `knowledge\u002Findex.md` (and give it an `index.md` like every other category) so the bundle map stays honest.\n\nDefault to the existing three. A new category is the exception, not the reflex.\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 the glossary, 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 the glossary inline\n\nWhen a term is resolved, write it to `knowledge\u002Fglossary\u002F` right there. Don't batch these up — capture them as they happen. Use the format in [CONTEXT-FORMAT.md](.\u002FCONTEXT-FORMAT.md).\n\nThe glossary 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\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* the knowledge bundle's glossary 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\nThe domain model lives in an **Open Knowledge Format (OKF)** knowledge bundle at `knowledge\u002F` in the repo root. Most repos have a single context:\n\n```\nknowledge\u002F\n├── index.md              ← bundle map (reserved: no frontmatter)\n├── log.md                ← change history, newest first (reserved: no frontmatter)\n├── glossary\u002F             ← one file per term (the glossary)\n│   ├── index.md\n│   ├── order.md\n│   └── customer.md\n└── adr\u002F                  ← one file per decision\n    ├── index.md\n    ├── adr-0001-event-sourced-orders.md\n    └── adr-0002-postgres-for-write-model.md\n```\n\nFor multiple bounded contexts, each context is a subdirectory inside the one bundle (`knowledge\u002Fordering\u002Fglossary\u002F`, `knowledge\u002Fbilling\u002Fglossary\u002F`, …) and `knowledge\u002Findex.md` is the context map. See [CONTEXT-FORMAT.md](.\u002FCONTEXT-FORMAT.md).\n\nCreate files lazily — only when you have something to write. If no `knowledge\u002Fglossary\u002F` exists, create it when the first term is resolved. If no `knowledge\u002Fadr\u002F` exists, create it when the first ADR is needed. Whenever knowledge changes, update the concept AND append to `knowledge\u002Flog.md`.\n\n### Extending the bundle (new concept categories)\n\n`glossary\u002F` and `adr\u002F` are the two categories every bundle has; `spec\u002F` (written by `\u002Fto-spec`) is the third canonical one. But OKF is an **open** format — `type` is a free field and the bundle is not limited to a fixed set of folders. When you meet a durable domain entity that genuinely fits none of them — a recurring *kind* of thing the project needs recorded in its own right — a new concept category is legitimate.\n\nDon't spin one up silently. When you judge a new category is warranted:\n\n1. **Propose it** — name the category, say what kind of entity it holds and why glossary\u002Fadr\u002Fprd don't fit.\n2. **Get the user's sanction** before creating the directory.\n3. **Register it** in `knowledge\u002Findex.md` (and give it an `index.md` like every other category) so the bundle map stays honest.\n\nDefault to the existing three. A new category is the exception, not the reflex.\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 the glossary, 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 the glossary inline\n\nWhen a term is resolved, write it to `knowledge\u002Fglossary\u002F` right there. Don't batch these up — capture them as they happen. Use the format in [CONTEXT-FORMAT.md](.\u002FCONTEXT-FORMAT.md).\n\nThe glossary 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\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","f3ea5610b95df91d4f50fb07d76b3fe1548e05f9",4,"https:\u002F\u002Fgithub.com\u002Fevist0\u002Fokf-matt-skills","https:\u002F\u002Fgithub.com\u002Fevist0","2026-07-09 03:00:22",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add evist0\u002Fokf-matt-skills --skill domain-modeling",{"tool":36,"command":37},"bunx","bunx skills add evist0\u002Fokf-matt-skills --skill domain-modeling",{"tool":39,"command":40},"pnpm","pnpm dlx skills add evist0\u002Fokf-matt-skills --skill domain-modeling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fevist0\u002Fokf-matt-skills\u002Fblob\u002Fmain\u002Fdomain-modeling\u002FSKILL.md",true,[44,50],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"ADR-FORMAT.md","REFERENCE","参考文档",3925,"https:\u002F\u002Fgithub.com\u002Fevist0\u002Fokf-matt-skills\u002Fblob\u002Fmain\u002Fdomain-modeling\u002FADR-FORMAT.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"CONTEXT-FORMAT.md",4515,"https:\u002F\u002Fgithub.com\u002Fevist0\u002Fokf-matt-skills\u002Fblob\u002Fmain\u002Fdomain-modeling\u002FCONTEXT-FORMAT.md",[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M788H00W6M0Y2S2VDGXN6XPY","write-skill","Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.","https:\u002F\u002Fgithub.com\u002Fevist0\u002Fokf-matt-skills\u002Fblob\u002Fmain\u002Fwrite-skill\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M788GY0ZW3K1Y1NWH0ES6S3F","which-skill","Ask which skill or flow fits your situation. A router over the skills in this repo.","https:\u002F\u002Fgithub.com\u002Fevist0\u002Fokf-matt-skills\u002Fblob\u002Fmain\u002Fwhich-skill\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M788GV67Q09BEARBX3PCKZB9","wayfinder","Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Fevist0\u002Fokf-matt-skills\u002Fblob\u002Fmain\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M788GPMNP9KQ02GC0AEVN22M","vet","Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue\u002FPRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".","https:\u002F\u002Fgithub.com\u002Fevist0\u002Fokf-matt-skills\u002Fblob\u002Fmain\u002Fvet\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M788GM23Z4V9DZH7WX5D1XHJ","triage","Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002Fevist0\u002Fokf-matt-skills\u002Fblob\u002Fmain\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M788GGNFSFAM4WNHNDQXRHD9","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 a local file, or native blocking links on a real tracker.","https:\u002F\u002Fgithub.com\u002Fevist0\u002Fokf-matt-skills\u002Fblob\u002Fmain\u002Fto-tickets\u002FSKILL.md",[],[]]