[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C8FS08P7QSNKHGTT5CB4TS":3,"skill-same:01M7C8FS08P7QSNKHGTT5CB4TS":64},{"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":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7C8FS08P7QSNKHGTT5CB4TS","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.","lutzseverino\u002Frepo-standards","lutzseverino","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F28309837?v=4","01M77NN0YKH0YYGY7W7ER23MX0","Jasper","01M7C8DB7P3FE7CNP4662DY55N",0,"MIT","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-standards\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\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\nA prompt or brief naming this skill is its invocation.\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\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, with the index [ADR-FORMAT.md](.\u002FADR-FORMAT.md) describes when the repo indexes its documentation directories.\n\nBefore your first edit to a glossary or ADR, work on a branch of your own in a checkout you own, such as a worktree or fresh clone, never in a shared checkout on the default branch. Each repository whose domain documents change gets its edits delivered as its contribution guide directs, such as one pull request.\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## Reads\n\nPaths are relative to the repository root.\n\n- `GLOSSARY.md`, or the root `GLOSSARY-MAP.md` that points to each context's\n  own `GLOSSARY.md`: the domain language. When `GLOSSARY-MAP.md` is missing,\n  the repository has a single context; when its `GLOSSARY.md` is missing,\n  create it once the first term is resolved.\n- `docs\u002Fadr\u002F`, holding `docs\u002Fadr\u002F\u003CNNNN>-\u003Cslug>.md` records, and each context's\n  own `docs\u002Fadr\u002F`: the decisions. When it is missing, create it when the first\n  ADR is needed.\n- `\u003Cdirectory>\u002FREADME.md`, such as `docs\u002Fadr\u002FREADME.md`: a documentation\n  directory's index. When the repository's documentation directories are\n  missing one, keep no ADR index; when only `docs\u002Fadr\u002FREADME.md` is missing,\n  create it with `docs\u002Fadr\u002F`.\n- `CONTRIBUTING.md`: how the repository delivers glossary and ADR edits, such\n  as one pull request. When it is missing, leave the edits on your own\n  branch.\n","A prompt or brief naming this skill is its invocation.\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\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, with the index [ADR-FORMAT.md](.\u002FADR-FORMAT.md) describes when the repo indexes its documentation directories.\n\nBefore your first edit to a glossary or ADR, work on a branch of your own in a checkout you own, such as a worktree or fresh clone, never in a shared checkout on the default branch. Each repository whose domain documents change gets its edits delivered as its contribution guide directs, such as one pull request.\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## Reads\n\nPaths are relative to the repository root.\n\n- `GLOSSARY.md`, or the root `GLOSSARY-MAP.md` that points to each context's\n  own `GLOSSARY.md`: the domain language. When `GLOSSARY-MAP.md` is missing,\n  the repository has a single context; when its `GLOSSARY.md` is missing,\n  create it once the first term is resolved.\n- `docs\u002Fadr\u002F`, holding `docs\u002Fadr\u002F\u003CNNNN>-\u003Cslug>.md` records, and each context's\n  own `docs\u002Fadr\u002F`: the decisions. When it is missing, create it when the first\n  ADR is needed.\n- `\u003Cdirectory>\u002FREADME.md`, such as `docs\u002Fadr\u002FREADME.md`: a documentation\n  directory's index. When the repository's documentation directories are\n  missing one, keep no ADR index; when only `docs\u002Fadr\u002FREADME.md` is missing,\n  create it with `docs\u002Fadr\u002F`.\n- `CONTRIBUTING.md`: how the repository delivers glossary and ADR edits, such\n  as one pull request. When it is missing, leave the edits on your own\n  branch.\n",{"name":5,"description":7},"main","1bcfc3fc1447b3f75448171015afea9bc1924344",".repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fdomain-modeling","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-standards","https:\u002F\u002Frepo-standards.com\u002F","https:\u002F\u002Fgithub.com\u002Flutzseverino","If Codex could write profile bios, you wouldn't be reading this. Or would you?","2026-11-15 04:40:53",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lutzseverino\u002Frepo-standards --skill domain-modeling",{"tool":38,"command":39},"bunx","bunx skills add lutzseverino\u002Frepo-standards --skill domain-modeling",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lutzseverino\u002Frepo-standards --skill domain-modeling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-standards\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fdomain-modeling\u002FSKILL.md",true,[46,52,56,60],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"ADR-FORMAT.md","REFERENCE","参考文档",3236,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-standards\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fdomain-modeling\u002FADR-FORMAT.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"agents\u002Fopenai.yaml",101,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-standards\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fdomain-modeling\u002Fagents\u002Fopenai.yaml",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"CREDITS.md",2311,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-standards\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fdomain-modeling\u002FCREDITS.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"GLOSSARY-FORMAT.md",2300,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-standards\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fdomain-modeling\u002FGLOSSARY-FORMAT.md",[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7C8HE06KZWSZ5SCM8DC25J5","repository-standards","In a project with .repo-standards\u002F, read the repository-wide installed rules and report available CLI and standards updates at the start of any work, including work that changes no file. Look up installed rules before changing a file.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-standards\u002Fblob\u002Fmain\u002Fskills\u002Frepository-standards\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7C8H9AQ9MK9BCZRAGEM9Z4V","author-standards","Create or revise local Repo Standards from confirmed preferences, including accepted checks, fixes, or ordinary-work author skills, or resume unfinished decisions from authoring notes and the current source.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-standards\u002Fblob\u002Fmain\u002Fskills\u002Fauthor-standards\u002FSKILL.md",[],[],{"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":19},"01M7C8H6JYDGZJK3AAV2TQ3WAV","adopt-repository-standards","Use when the user wants to adopt a standards source or adopt, set up, or apply shared repository conventions or standards in a repository.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-standards\u002Fblob\u002Fmain\u002Fskills\u002Fadopt-repository-standards\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":19},"01M7C8H4PR4Q7YHGYFNABR1KRJ","review","Review project changes against its documented conventions.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-standards\u002Fblob\u002Fmain\u002Fexamples\u002Falice\u002Fdefaults\u002Fskills\u002Freview\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":19},"01M7C8H2KXV3NH59JP9YFXNXK3","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-standards\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fwriting-for-agents\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":19},"01M7C8GZJR704V32CGRE05MHBF","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\u002Flutzseverino\u002Frepo-standards\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]