[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CATAP2K1MHYY5WBXND9VG5":3,"skill-same:01M6CATAP2K1MHYY5WBXND9VG5":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":64},"01M6CATAP2K1MHYY5WBXND9VG5","ubiquitous-language",null,"Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\".","jleechanorg\u002Fjleechan-skills","jleechanorg","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F221404966?v=4","01M6C1VJ99XG950X1DWPEBCBGX","01M6C1VJDK5YVDNT3362RT5WSB",6,"MIT","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Fubiquitous-language\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"ubiquitous language","language","when","create","true","canonical","style","define","harden","domain model","domain","terminology","conversation","build","use","extract","user","glossary","model","terms","ddd","2026-11-10 10:12:30",false,"---\nname: ubiquitous-language\ndescription: Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\".\ndisable-model-invocation: true\n---\n\n# Ubiquitous Language\n\nExtract and formalize domain terminology from the current conversation into a consistent glossary, saved to a local file.\n\n## Process\n\n1. **Scan the conversation** for domain-relevant nouns, verbs, and concepts\n2. **Identify problems**:\n   - Same word used for different concepts (ambiguity)\n   - Different words used for the same concept (synonyms)\n   - Vague or overloaded terms\n3. **Propose a canonical glossary** with opinionated term choices\n4. **Write to `UBIQUITOUS_LANGUAGE.md`** in the working directory using the format below\n5. **Output a summary** inline in the conversation\n\n## Output Format\n\nWrite a `UBIQUITOUS_LANGUAGE.md` file with this structure:\n\n```md\n# Ubiquitous Language\n\n## Order lifecycle\n\n| Term        | Definition                                              | Aliases to avoid      |\n| ----------- | ------------------------------------------------------- | --------------------- |\n| **Order**   | A customer's request to purchase one or more items      | Purchase, transaction |\n| **Invoice** | A request for payment sent to a customer after delivery | Bill, payment request |\n\n## People\n\n| Term         | Definition                                  | Aliases to avoid       |\n| ------------ | ------------------------------------------- | ---------------------- |\n| **Customer** | A person or organization that places orders | Client, buyer, account |\n| **User**     | An authentication identity in the system    | Login, account         |\n\n## Relationships\n\n- An **Invoice** belongs to exactly one **Customer**\n- An **Order** produces one or more **Invoices**\n\n## Example dialogue\n\n> **Dev:** \"When a **Customer** places an **Order**, do we create the **Invoice** immediately?\"\n> **Domain expert:** \"No — an **Invoice** is only generated once a **Fulfillment** is confirmed. A single **Order** can produce multiple **Invoices** if items ship in separate **Shipments**.\"\n> **Dev:** \"So if a **Shipment** is cancelled before dispatch, no **Invoice** exists for it?\"\n> **Domain expert:** \"Exactly. The **Invoice** lifecycle is tied to the **Fulfillment**, not the **Order**.\"\n\n## Flagged ambiguities\n\n- \"account\" was used to mean both **Customer** and **User** — these are distinct concepts: a **Customer** places orders, while a **User** is an authentication identity that may or may not represent a **Customer**.\n```\n\n## Rules\n\n- **Be opinionated.** When multiple words exist for the same concept, pick the best one and list the others as aliases to avoid.\n- **Flag conflicts explicitly.** If a term is used ambiguously in the conversation, call it out in the \"Flagged ambiguities\" section with a clear recommendation.\n- **Only include terms relevant for domain experts.** Skip the names of modules or classes unless they have meaning in the domain language.\n- **Keep definitions tight.** One sentence max. Define what it IS, not what it does.\n- **Show relationships.** Use bold term names and express cardinality where obvious.\n- **Only include domain terms.** Skip generic programming concepts (array, function, endpoint) unless they have domain-specific meaning.\n- **Group terms into multiple tables** when natural clusters emerge (e.g. by subdomain, lifecycle, or actor). Each group gets its own heading and table. If all terms belong to a single cohesive domain, one table is fine — don't force groupings.\n- **Write an example dialogue.** A short conversation (3-5 exchanges) between a dev and a domain expert that demonstrates how the terms interact naturally. The dialogue should clarify boundaries between related concepts and show terms being used precisely.\n\n\u003Cexample>\n\n## Example dialogue\n\n> **Dev:** \"How do I test the **sync service** without Docker?\"\n\n> **Domain expert:** \"Provide the **filesystem layer** instead of the **Docker layer**. It implements the same **Sandbox service** interface but uses a local directory as the **sandbox**.\"\n\n> **Dev:** \"So **sync-in** still creates a **bundle** and unpacks it?\"\n\n> **Domain expert:** \"Exactly. The **sync service** doesn't know which layer it's talking to. It calls `exec` and `copyIn` — the **filesystem layer** just runs those as local shell commands.\"\n\n\u003C\u002Fexample>\n\n## Re-running\n\nWhen invoked again in the same conversation:\n\n1. Read the existing `UBIQUITOUS_LANGUAGE.md`\n2. Incorporate any new terms from subsequent discussion\n3. Update definitions if understanding has evolved\n4. Re-flag any new ambiguities\n5. Rewrite the example dialogue to incorporate new terms\n","# Ubiquitous Language\n\nExtract and formalize domain terminology from the current conversation into a consistent glossary, saved to a local file.\n\n## Process\n\n1. **Scan the conversation** for domain-relevant nouns, verbs, and concepts\n2. **Identify problems**:\n   - Same word used for different concepts (ambiguity)\n   - Different words used for the same concept (synonyms)\n   - Vague or overloaded terms\n3. **Propose a canonical glossary** with opinionated term choices\n4. **Write to `UBIQUITOUS_LANGUAGE.md`** in the working directory using the format below\n5. **Output a summary** inline in the conversation\n\n## Output Format\n\nWrite a `UBIQUITOUS_LANGUAGE.md` file with this structure:\n\n```md\n# Ubiquitous Language\n\n## Order lifecycle\n\n| Term        | Definition                                              | Aliases to avoid      |\n| ----------- | ------------------------------------------------------- | --------------------- |\n| **Order**   | A customer's request to purchase one or more items      | Purchase, transaction |\n| **Invoice** | A request for payment sent to a customer after delivery | Bill, payment request |\n\n## People\n\n| Term         | Definition                                  | Aliases to avoid       |\n| ------------ | ------------------------------------------- | ---------------------- |\n| **Customer** | A person or organization that places orders | Client, buyer, account |\n| **User**     | An authentication identity in the system    | Login, account         |\n\n## Relationships\n\n- An **Invoice** belongs to exactly one **Customer**\n- An **Order** produces one or more **Invoices**\n\n## Example dialogue\n\n> **Dev:** \"When a **Customer** places an **Order**, do we create the **Invoice** immediately?\"\n> **Domain expert:** \"No — an **Invoice** is only generated once a **Fulfillment** is confirmed. A single **Order** can produce multiple **Invoices** if items ship in separate **Shipments**.\"\n> **Dev:** \"So if a **Shipment** is cancelled before dispatch, no **Invoice** exists for it?\"\n> **Domain expert:** \"Exactly. The **Invoice** lifecycle is tied to the **Fulfillment**, not the **Order**.\"\n\n## Flagged ambiguities\n\n- \"account\" was used to mean both **Customer** and **User** — these are distinct concepts: a **Customer** places orders, while a **User** is an authentication identity that may or may not represent a **Customer**.\n```\n\n## Rules\n\n- **Be opinionated.** When multiple words exist for the same concept, pick the best one and list the others as aliases to avoid.\n- **Flag conflicts explicitly.** If a term is used ambiguously in the conversation, call it out in the \"Flagged ambiguities\" section with a clear recommendation.\n- **Only include terms relevant for domain experts.** Skip the names of modules or classes unless they have meaning in the domain language.\n- **Keep definitions tight.** One sentence max. Define what it IS, not what it does.\n- **Show relationships.** Use bold term names and express cardinality where obvious.\n- **Only include domain terms.** Skip generic programming concepts (array, function, endpoint) unless they have domain-specific meaning.\n- **Group terms into multiple tables** when natural clusters emerge (e.g. by subdomain, lifecycle, or actor). Each group gets its own heading and table. If all terms belong to a single cohesive domain, one table is fine — don't force groupings.\n- **Write an example dialogue.** A short conversation (3-5 exchanges) between a dev and a domain expert that demonstrates how the terms interact naturally. The dialogue should clarify boundaries between related concepts and show terms being used precisely.\n\n\u003Cexample>\n\n## Example dialogue\n\n> **Dev:** \"How do I test the **sync service** without Docker?\"\n\n> **Domain expert:** \"Provide the **filesystem layer** instead of the **Docker layer**. It implements the same **Sandbox service** interface but uses a local directory as the **sandbox**.\"\n\n> **Dev:** \"So **sync-in** still creates a **bundle** and unpacks it?\"\n\n> **Domain expert:** \"Exactly. The **sync service** doesn't know which layer it's talking to. It calls `exec` and `copyIn` — the **filesystem layer** just runs those as local shell commands.\"\n\n\u003C\u002Fexample>\n\n## Re-running\n\nWhen invoked again in the same conversation:\n\n1. Read the existing `UBIQUITOUS_LANGUAGE.md`\n2. Incorporate any new terms from subsequent discussion\n3. Update definitions if understanding has evolved\n4. Re-flag any new ambiguities\n5. Rewrite the example dialogue to incorporate new terms\n",{"name":5,"description":7,"disable-model-invocation":44},true,"main","05df7380981a2c4af868ce0fa57962ae0eea62a9","hermes\u002Fskills\u002Fubiquitous-language",0,"https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills","https:\u002F\u002Fgithub.com\u002Fjleechanorg","2026-11-11 22:19:36",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":44},[54,57,60],{"tool":55,"command":56},"npx","npx skills add jleechanorg\u002Fjleechan-skills --skill ubiquitous-language",{"tool":58,"command":59},"bunx","bunx skills add jleechanorg\u002Fjleechan-skills --skill ubiquitous-language",{"tool":61,"command":62},"pnpm","pnpm dlx skills add jleechanorg\u002Fjleechan-skills --skill ubiquitous-language","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Fubiquitous-language\u002FSKILL.md",[65],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"agents\u002Fopenai.yaml","REFERENCE","参考文档",146,"https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Fubiquitous-language\u002Fagents\u002Fopenai.yaml",[72,87,109,123,135,151],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":39},"01M716Y5MTJ6GYJZ2ATXCJK8G4","instinct","Use when the user invokes \u002Finstinct or \u002Fin, or asks to \"message Instinct\", \"ask Instinct\", \"tell Instinct\", \"check Instinct\", or read replies from the configured peer assistant. iMessage first, WhatsApp Web as fallback.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Finstinct\u002FSKILL.md",[],[74,34,20,79,80,32,81,82,83,84,85,86],"replies","check","identity","whatsapp","gmail","read","message","ask",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":98,"publishedAt":39},"01M716Y4HF7FVVMJSA2CCVN5VF","hr","Compatibility alias for history-resume; produce the same fresh-state, provenance-aware resume briefing.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhr\u002FSKILL.md",[93],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[89,99,100,101,102,103,104,105,106,107,108],"resume","compatibility","provenance","for","history","produce","alias","briefing","state","fresh",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":116,"publishedAt":39},"01M716Y1FFNFKFJYYKF8HQA6T8","history-resume","Resume briefing for the current repository branch or worktree using fresh state and admitted history sources.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhistory-resume\u002FSKILL.md",[115],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},[103,99,117,118,34,119,106,120,102,121,122,107,108],"history resume","branch","analysis","repository","worktree","sources",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":39},"01M716XWXJ8EPHK4RH9T14TR85","grok","Alias for the canonical grokbot browser conversation workflow; \u002Fgrok talks to the Grok bot the same way \u002Fdot talks to Dot.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgrok\u002FSKILL.md",[],[125,130,131,132,102,23,105,30,133,134],"dot","bot","workflow","browser","grokbot",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":39},"01M70N9Q07DTE0EW5KFXMMMSJ0","codexa-bench","Compare `codexa` and normal `codex` on a fair split of comparable work by default; use `--strict` for duplicate runs of the exact same task.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcodexa-bench\u002FSKILL.md",[],[142,143,144,32,145,102,146,147,148,149,150],"codexa bench","work","split","default","duplicate","task","compare","normal","codex",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":155,"licenseFileUrl":156,"sourceHtmlUrl":157,"categories":158,"keywords":170,"publishedAt":39},"01M6C24S2X60SP8BBFGAEKPEGW","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffrontend-design\u002FSKILL.md",[159,164,167],{"categoryNo":160,"categoryName":161,"taxonomyType":162,"taxonomyTypeDesc":163},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":165,"categoryName":166,"taxonomyType":162,"taxonomyTypeDesc":163},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":168,"categoryName":169,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000032","设计师",[171,172,173,32,174,175,176,34,177,178,179,180,181,182,183,184,185,186,187,188,189,21,190,191,192,193,20,194],"frontend","design","frontend design","generic","ui design","react","html","components","code","artifacts","ui","aesthetics","Production","web components","landing","applications","quality","web","css","examples","with","react components","web ui","pages"]