[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78H7RY8MSDPSZXN6A4EMR1N":3,"skill-same:01M78H7RY8MSDPSZXN6A4EMR1N":61},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M78H7RY8MSDPSZXN6A4EMR1N","domain-modeling",null,"构建并打磨项目的 domain model。在讨论代码库术语、编写或编辑 GLOSSARY.md、或记录或编辑 ADR 时使用。","toRolex\u002Frolex-skills","toRolex","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F171526267?v=4","01M78H6W9BVJ5TBK7APN5HFBJF","Rolex","01M78H6WAC60FGNASCYJAJM7VW",1,"MIT","https:\u002F\u002Fgithub.com\u002FtoRolex\u002Frolex-skills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fdomain-modeling\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: domain-modeling\ndescription: 构建并打磨项目的 domain model。在讨论代码库术语、编写或编辑 GLOSSARY.md、或记录或编辑 ADR 时使用。\n---\n\n# Domain Modeling\n\n在设计中主动构建并打磨项目的 domain model。这是一门 *主动* 的功夫：质疑术语、编造 edge case 场景，并在 glossary 和 decisions 一经成形时立刻把它们写下来。（仅仅 *读* `GLOSSARY.md` 来取词汇并不是这个 skill：那是任何 skill 都能做到的一行习惯。这个 skill 适用于你在*改变*模型，而不只是消费它。）\n\n## 文件结构\n\n大多数仓库只有一个 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\n如果根目录存在 `GLOSSARY-MAP.md`，说明仓库有多个 contexts。map 会指出每个 context 所在的位置：\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\n懒创建文件：只在你有东西要写时才创建。如果不存在 `GLOSSARY.md`，在第一个术语被确定时创建它。如果不存在 `docs\u002Fadr\u002F`，在第一个 ADR 需要时创建它。\n\n## 会话期间\n\n### 用 glossary 提出质疑\n\n当用户使用一个与 `GLOSSARY.md` 中现有语言冲突的术语时，立刻指出来。「你的 glossary 把 'cancellation' 定义为 X，但你看起来想说的是 Y。到底是哪个？」\n\n### 打磨模糊的语言\n\n当用户使用模糊或过载的术语时，提出一个精确的规范术语。「你说的是 'account'：你指的是 Customer 还是 User？两者是不同的东西。」\n\n### 讨论具体场景\n\n当讨论领域关系时，用具体场景做压力测试。编造能探测 edge cases、迫使用户对概念之间的边界做到精确的场景。\n\n### 与代码交叉核对\n\n当用户描述某件事如何运作时，检查代码是否一致。如果发现矛盾，就把它摆出来：「你的代码取消的是整个 Orders，但你刚才说可以部分取消。哪个才是对的？」\n\n### 就地更新 GLOSSARY.md\n\n当一个术语被确定时，就地更新 `GLOSSARY.md`。不要攒起来：随时发生随时记录。使用 [GLOSSARY-FORMAT.md](.\u002FGLOSSARY-FORMAT.md) 中的格式。\n\n`GLOSSARY.md` 应该完全不含实现细节。不要把 `GLOSSARY.md` 当作 spec、草稿本或实现决策的仓库。它只是一个 glossary，仅此而已。\n\n### 审慎地提供 ADRs\n\n只有以下三条全部成立时才主动提出创建 ADR：\n\n1. **Hard to reverse**：日后改变主意的代价是实质性的\n2. **Surprising without context**：未来的读者会疑惑\"他们为什么这样做？\"\n3. **The result of a real trade-off**：存在真正的备选方案，而你基于特定理由选了一个\n\n三条缺一，就跳过 ADR。使用 [ADR-FORMAT.md](.\u002FADR-FORMAT.md) 中的格式。\n","# Domain Modeling\n\n在设计中主动构建并打磨项目的 domain model。这是一门 *主动* 的功夫：质疑术语、编造 edge case 场景，并在 glossary 和 decisions 一经成形时立刻把它们写下来。（仅仅 *读* `GLOSSARY.md` 来取词汇并不是这个 skill：那是任何 skill 都能做到的一行习惯。这个 skill 适用于你在*改变*模型，而不只是消费它。）\n\n## 文件结构\n\n大多数仓库只有一个 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\n如果根目录存在 `GLOSSARY-MAP.md`，说明仓库有多个 contexts。map 会指出每个 context 所在的位置：\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\n懒创建文件：只在你有东西要写时才创建。如果不存在 `GLOSSARY.md`，在第一个术语被确定时创建它。如果不存在 `docs\u002Fadr\u002F`，在第一个 ADR 需要时创建它。\n\n## 会话期间\n\n### 用 glossary 提出质疑\n\n当用户使用一个与 `GLOSSARY.md` 中现有语言冲突的术语时，立刻指出来。「你的 glossary 把 'cancellation' 定义为 X，但你看起来想说的是 Y。到底是哪个？」\n\n### 打磨模糊的语言\n\n当用户使用模糊或过载的术语时，提出一个精确的规范术语。「你说的是 'account'：你指的是 Customer 还是 User？两者是不同的东西。」\n\n### 讨论具体场景\n\n当讨论领域关系时，用具体场景做压力测试。编造能探测 edge cases、迫使用户对概念之间的边界做到精确的场景。\n\n### 与代码交叉核对\n\n当用户描述某件事如何运作时，检查代码是否一致。如果发现矛盾，就把它摆出来：「你的代码取消的是整个 Orders，但你刚才说可以部分取消。哪个才是对的？」\n\n### 就地更新 GLOSSARY.md\n\n当一个术语被确定时，就地更新 `GLOSSARY.md`。不要攒起来：随时发生随时记录。使用 [GLOSSARY-FORMAT.md](.\u002FGLOSSARY-FORMAT.md) 中的格式。\n\n`GLOSSARY.md` 应该完全不含实现细节。不要把 `GLOSSARY.md` 当作 spec、草稿本或实现决策的仓库。它只是一个 glossary，仅此而已。\n\n### 审慎地提供 ADRs\n\n只有以下三条全部成立时才主动提出创建 ADR：\n\n1. **Hard to reverse**：日后改变主意的代价是实质性的\n2. **Surprising without context**：未来的读者会疑惑\"他们为什么这样做？\"\n3. **The result of a real trade-off**：存在真正的备选方案，而你基于特定理由选了一个\n\n三条缺一，就跳过 ADR。使用 [ADR-FORMAT.md](.\u002FADR-FORMAT.md) 中的格式。\n",{"name":5,"description":7},"main","5648606410e64c6ebad383fa37b866fcd14718cf","skills\u002Fengineering\u002Fdomain-modeling",0,"https:\u002F\u002Fgithub.com\u002FtoRolex\u002Frolex-skills","https:\u002F\u002Fgithub.com\u002FtoRolex","luolie3@mail2.sysu.edu.cn","I'm Luo Lie from SYSU. Mathematics-trained builder for agentic AI systems and real-world products.","2026-11-03 15:28:15",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add toRolex\u002Frolex-skills --skill domain-modeling",{"tool":39,"command":40},"bunx","bunx skills add toRolex\u002Frolex-skills --skill domain-modeling",{"tool":42,"command":43},"pnpm","pnpm dlx skills add toRolex\u002Frolex-skills --skill domain-modeling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FtoRolex\u002Frolex-skills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fdomain-modeling\u002FSKILL.md",true,[47,53,57],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"ADR-FORMAT.md","REFERENCE","参考文档",2559,"https:\u002F\u002Fgithub.com\u002FtoRolex\u002Frolex-skills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fdomain-modeling\u002FADR-FORMAT.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"agents\u002Fopenai.yaml",101,"https:\u002F\u002Fgithub.com\u002FtoRolex\u002Frolex-skills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fdomain-modeling\u002Fagents\u002Fopenai.yaml",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"GLOSSARY-FORMAT.md",2342,"https:\u002F\u002Fgithub.com\u002FtoRolex\u002Frolex-skills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fdomain-modeling\u002FGLOSSARY-FORMAT.md",[62,69,76,83,90,97],{"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},"01M78HA978AVPWGFE3PR9RNJ9G","writing-great-skills","Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.","https:\u002F\u002Fgithub.com\u002FtoRolex\u002Frolex-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fwriting-great-skills\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},"01M78HA7737MNQ4411A7SZWPJQ","writing-for-agents","覆盖创建、修改与审核 agent 指令规则、路由及指针文档（如 skill、AGENTS.md、CLAUDE.md）。","https:\u002F\u002Fgithub.com\u002FtoRolex\u002Frolex-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fwriting-for-agents\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},"01M78HA62NC1NZNAEZ26784495","wait-what","停下。上一条消息没有说清楚：重新讲一遍。","https:\u002F\u002Fgithub.com\u002FtoRolex\u002Frolex-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fwait-what\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},"01M78HA4NX5KBJ7WQ69SR25QHW","to-questionnaire","把一个你无法完全回答的决策，变成一个让其他人填写的问题单。","https:\u002F\u002Fgithub.com\u002FtoRolex\u002Frolex-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fto-questionnaire\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},"01M78HA2RTESFTRTNA7ZZNVVXS","teach-me","在教学工作区内教授用户一项新技能或概念。","https:\u002F\u002Fgithub.com\u002FtoRolex\u002Frolex-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fteach-me\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M78HA187DQB10VDJ4G89F540","handoff","将当前对话压缩为 handoff 文档，供另一个 agent 接续。","https:\u002F\u002Fgithub.com\u002FtoRolex\u002Frolex-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fhandoff\u002FSKILL.md",[],[]]