[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AWW55WM5D9TR58A6TMP9PC":3,"skill-same:01M7AWW55WM5D9TR58A6TMP9PC":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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7AWW55WM5D9TR58A6TMP9PC","domain-modeling",null,"Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.","KunoLu\u002Fsbtd-plugins","KunoLu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F60886434?v=4","01M7AWBJNA6JJ6KBD84KR936JH","640","01M7AWBJP0V2KGW7VRBH4HY22M",195,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated-omp\u002Fonboard\u002Fruntime\u002Fassets\u002Fexternal-skills\u002Fstable\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 CONTEXT.md, or recording or editing an ADR.\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* `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.)\n\n## File structure\n\nMost repos have a single context:\n\n```\n\u002F\n├── CONTEXT.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 `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives:\n\n```\n\u002F\n├── CONTEXT-MAP.md\n├── docs\u002F\n│   └── adr\u002F                          ← system-wide decisions\n├── src\u002F\n│   ├── ordering\u002F\n│   │   ├── CONTEXT.md\n│   │   └── docs\u002Fadr\u002F                 ← context-specific decisions\n│   └── billing\u002F\n│       ├── CONTEXT.md\n│       └── docs\u002Fadr\u002F\n```\n\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.\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 `CONTEXT.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 CONTEXT.md inline\n\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).\n\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.\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* `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.)\n\n## File structure\n\nMost repos have a single context:\n\n```\n\u002F\n├── CONTEXT.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 `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives:\n\n```\n\u002F\n├── CONTEXT-MAP.md\n├── docs\u002F\n│   └── adr\u002F                          ← system-wide decisions\n├── src\u002F\n│   ├── ordering\u002F\n│   │   ├── CONTEXT.md\n│   │   └── docs\u002Fadr\u002F                 ← context-specific decisions\n│   └── billing\u002F\n│       ├── CONTEXT.md\n│       └── docs\u002Fadr\u002F\n```\n\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.\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 `CONTEXT.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 CONTEXT.md inline\n\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).\n\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.\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","0d9331bd7d64c28dea368fd4385fd009809d58da","packages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated-omp\u002Fonboard\u002Fruntime\u002Fassets\u002Fexternal-skills\u002Fstable\u002Fskills\u002Fdomain-modeling",1,"https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins","https:\u002F\u002Fgithub.com\u002FKunoLu","2026-11-05 11:57:54",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add KunoLu\u002Fsbtd-plugins --skill domain-modeling",{"tool":37,"command":38},"bunx","bunx skills add KunoLu\u002Fsbtd-plugins --skill domain-modeling",{"tool":40,"command":41},"pnpm","pnpm dlx skills add KunoLu\u002Fsbtd-plugins --skill domain-modeling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated-omp\u002Fonboard\u002Fruntime\u002Fassets\u002Fexternal-skills\u002Fstable\u002Fskills\u002Fdomain-modeling\u002FSKILL.md",true,[45,51,55],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"ADR-FORMAT.md","REFERENCE","参考文档",2733,"https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated-omp\u002Fonboard\u002Fruntime\u002Fassets\u002Fexternal-skills\u002Fstable\u002Fskills\u002Fdomain-modeling\u002FADR-FORMAT.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"agents\u002Fopenai.yaml",101,"https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated-omp\u002Fonboard\u002Fruntime\u002Fassets\u002Fexternal-skills\u002Fstable\u002Fskills\u002Fdomain-modeling\u002Fagents\u002Fopenai.yaml",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"CONTEXT-FORMAT.md",2290,"https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated-omp\u002Fonboard\u002Fruntime\u002Fassets\u002Fexternal-skills\u002Fstable\u002Fskills\u002Fdomain-modeling\u002FCONTEXT-FORMAT.md",[60,67,74,82,90,98],{"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},"01M7AX886G1MY416H73C125QZY","gherkin-bdd","Use when adding, changing, reviewing, testing, synchronizing, or read-only ingesting user-visible behavior with BDD, Gherkin, Given\u002FWhen\u002FThen scenarios, .feature files, acceptance criteria, knowledge catalogs, or bug-fix behavior specs.","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fomp-overlays\u002Fonboard\u002Fruntime\u002Ftemplates\u002Fskills\u002Fgherkin-bdd\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},"01M7AX84YZXTS7PR2WSMYJACTZ","sbtd-workflow-onboard","Checks, installs, or resets SBTD workflow tools, global Skills, managed AGENTS templates, and per-project configuration for local project roots in Oh My Pi.","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fomp-overlays\u002Fonboard\u002Fruntime\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":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7AX80VRAYPPHAN1XN3X7G3V","web-ui-autotest-generator","从前端和后端源码中生成可维护的 Web UI 自动化测试。适用于分析页面、路由、组件、接口、用户流程，生成 Playwright UI 测试，运行测试，生成中文报告，并自检页面功能和跨页面逻辑是否被独立测试资产覆盖。 Generate maintainable Web UI automated tests from frontend and backend source code. Use for analyzing pages, routes, components, APIs, and user flows; generating and running Playwright UI tests; producing Chinese test reports; and checking whether page features and cross-page logic are covered by independent test assets.","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated\u002Fonboard\u002Fruntime\u002Ftemplates\u002Fskills\u002Fweb-ui-autotest-generator\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated\u002Fonboard\u002Fruntime\u002Ftemplates\u002Fskills\u002Fweb-ui-autotest-generator\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7AX7THTKH5DJPGH67M3SQ0Q","seo-geo","SEO & GEO (Generative Engine Optimization) for websites. Analyze keywords, generate schema markup, optimize for AI search engines (ChatGPT, Perplexity, Gemini, Copilot, Claude) and traditional search (Google, Bing). Use when user wants to improve search visibility, search optimization, search ranking, AI visibility, ChatGPT ranking, Google AI Overview, indexing, JSON-LD, meta tags, or keyword research.","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated\u002Fonboard\u002Fruntime\u002Ftemplates\u002Fskills\u002Fseo-geo\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated\u002Fonboard\u002Fruntime\u002Ftemplates\u002Fskills\u002Fseo-geo\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":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7AX7P70M14ZRN5BRHC8BHP3","sbtd-task","Use for SBTD task execution and continuation, explicit default\u002Flite\u002Fstrict mode selection, task records and status changes, cross-session recovery, and task handoffs. Load strict gates only for strict tasks; ordinary questions and read-only work do not create task files.","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated\u002Fonboard\u002Fruntime\u002Ftemplates\u002Fskills\u002Fsbtd-task\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated\u002Fonboard\u002Fruntime\u002Ftemplates\u002Fskills\u002Fsbtd-task\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7AX7GX3NPZ19J2T9EMFC63H","project-validation","Use after code changes to choose and run validation commands for Node, JavaScript, TypeScript, Python, Go, Dart, Java, Kotlin, C++, Swift, or Objective-C projects. Prefer project-defined commands and report skipped checks and risks.","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated\u002Fonboard\u002Fruntime\u002Ftemplates\u002Fskills\u002Fproject-validation\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FKunoLu\u002Fsbtd-plugins\u002Fblob\u002Fmain\u002Fpackages\u002Fomp-sbtd\u002Fupstream\u002Fgenerated\u002Fonboard\u002Fruntime\u002Ftemplates\u002Fskills\u002Fproject-validation\u002FSKILL.md",[],[]]