[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75YBA6M490WDS3SFPS0G5CC":3,"skill-same:01M75YBA6M490WDS3SFPS0G5CC":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":46},"01M75YBA6M490WDS3SFPS0G5CC","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\".","sachahjkl\u002Fdw","sachahjkl","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F32895534?v=4","01M75YABKP7VH9F8QHR38CY2F6","Sacha","01M75YABMCP612W469EH3GHTQ6",1,"MIT","https:\u002F\u002Fgithub.com\u002Fsachahjkl\u002Fdw\u002Fblob\u002Fmaster\u002Fdocs\u002Freferences\u002Fagents\u002Fskills\u002Fubiquitous-language\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\r\nname: ubiquitous-language\r\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\".\r\ndisable-model-invocation: true\r\n---\r\n\r\n# Ubiquitous Language\r\n\r\nExtract and formalize domain terminology from the current conversation into a consistent glossary, saved to a local file.\r\n\r\n## Process\r\n\r\n1. **Scan the conversation** for domain-relevant nouns, verbs, and concepts\r\n2. **Identify problems**:\r\n   - Same word used for different concepts (ambiguity)\r\n   - Different words used for the same concept (synonyms)\r\n   - Vague or overloaded terms\r\n3. **Propose a canonical glossary** with opinionated term choices\r\n4. **Write to `UBIQUITOUS_LANGUAGE.md`** in the working directory using the format below\r\n5. **Output a summary** inline in the conversation\r\n\r\n## Output Format\r\n\r\nWrite a `UBIQUITOUS_LANGUAGE.md` file with this structure:\r\n\r\n```md\r\n# Ubiquitous Language\r\n\r\n## Order lifecycle\r\n\r\n| Term        | Definition                                              | Aliases to avoid      |\r\n| ----------- | ------------------------------------------------------- | --------------------- |\r\n| **Order**   | A customer's request to purchase one or more items      | Purchase, transaction |\r\n| **Invoice** | A request for payment sent to a customer after delivery | Bill, payment request |\r\n\r\n## People\r\n\r\n| Term         | Definition                                  | Aliases to avoid       |\r\n| ------------ | ------------------------------------------- | ---------------------- |\r\n| **Customer** | A person or organization that places orders | Client, buyer, account |\r\n| **User**     | An authentication identity in the system    | Login, account         |\r\n\r\n## Relationships\r\n\r\n- An **Invoice** belongs to exactly one **Customer**\r\n- An **Order** produces one or more **Invoices**\r\n\r\n## Example dialogue\r\n\r\n> **Dev:** \"When a **Customer** places an **Order**, do we create the **Invoice** immediately?\"\r\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**.\"\r\n> **Dev:** \"So if a **Shipment** is cancelled before dispatch, no **Invoice** exists for it?\"\r\n> **Domain expert:** \"Exactly. The **Invoice** lifecycle is tied to the **Fulfillment**, not the **Order**.\"\r\n\r\n## Flagged ambiguities\r\n\r\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**.\r\n```\r\n\r\n## Rules\r\n\r\n- **Be opinionated.** When multiple words exist for the same concept, pick the best one and list the others as aliases to avoid.\r\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.\r\n- **Only include terms relevant for domain experts.** Skip the names of modules or classes unless they have meaning in the domain language.\r\n- **Keep definitions tight.** One sentence max. Define what it IS, not what it does.\r\n- **Show relationships.** Use bold term names and express cardinality where obvious.\r\n- **Only include domain terms.** Skip generic programming concepts (array, function, endpoint) unless they have domain-specific meaning.\r\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.\r\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.\r\n\r\n\u003Cexample>\r\n\r\n## Example dialogue\r\n\r\n> **Dev:** \"How do I test the **sync service** without Docker?\"\r\n\r\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**.\"\r\n\r\n> **Dev:** \"So **sync-in** still creates a **bundle** and unpacks it?\"\r\n\r\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.\"\r\n\r\n\u003C\u002Fexample>\r\n\r\n## Re-running\r\n\r\nWhen invoked again in the same conversation:\r\n\r\n1. Read the existing `UBIQUITOUS_LANGUAGE.md`\r\n2. Incorporate any new terms from subsequent discussion\r\n3. Update definitions if understanding has evolved\r\n4. Re-flag any new ambiguities\r\n5. Rewrite the example dialogue to incorporate new terms\r\n","# Ubiquitous Language\r\n\r\nExtract and formalize domain terminology from the current conversation into a consistent glossary, saved to a local file.\r\n\r\n## Process\r\n\r\n1. **Scan the conversation** for domain-relevant nouns, verbs, and concepts\r\n2. **Identify problems**:\r\n   - Same word used for different concepts (ambiguity)\r\n   - Different words used for the same concept (synonyms)\r\n   - Vague or overloaded terms\r\n3. **Propose a canonical glossary** with opinionated term choices\r\n4. **Write to `UBIQUITOUS_LANGUAGE.md`** in the working directory using the format below\r\n5. **Output a summary** inline in the conversation\r\n\r\n## Output Format\r\n\r\nWrite a `UBIQUITOUS_LANGUAGE.md` file with this structure:\r\n\r\n```md\r\n# Ubiquitous Language\r\n\r\n## Order lifecycle\r\n\r\n| Term        | Definition                                              | Aliases to avoid      |\r\n| ----------- | ------------------------------------------------------- | --------------------- |\r\n| **Order**   | A customer's request to purchase one or more items      | Purchase, transaction |\r\n| **Invoice** | A request for payment sent to a customer after delivery | Bill, payment request |\r\n\r\n## People\r\n\r\n| Term         | Definition                                  | Aliases to avoid       |\r\n| ------------ | ------------------------------------------- | ---------------------- |\r\n| **Customer** | A person or organization that places orders | Client, buyer, account |\r\n| **User**     | An authentication identity in the system    | Login, account         |\r\n\r\n## Relationships\r\n\r\n- An **Invoice** belongs to exactly one **Customer**\r\n- An **Order** produces one or more **Invoices**\r\n\r\n## Example dialogue\r\n\r\n> **Dev:** \"When a **Customer** places an **Order**, do we create the **Invoice** immediately?\"\r\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**.\"\r\n> **Dev:** \"So if a **Shipment** is cancelled before dispatch, no **Invoice** exists for it?\"\r\n> **Domain expert:** \"Exactly. The **Invoice** lifecycle is tied to the **Fulfillment**, not the **Order**.\"\r\n\r\n## Flagged ambiguities\r\n\r\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**.\r\n```\r\n\r\n## Rules\r\n\r\n- **Be opinionated.** When multiple words exist for the same concept, pick the best one and list the others as aliases to avoid.\r\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.\r\n- **Only include terms relevant for domain experts.** Skip the names of modules or classes unless they have meaning in the domain language.\r\n- **Keep definitions tight.** One sentence max. Define what it IS, not what it does.\r\n- **Show relationships.** Use bold term names and express cardinality where obvious.\r\n- **Only include domain terms.** Skip generic programming concepts (array, function, endpoint) unless they have domain-specific meaning.\r\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.\r\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.\r\n\r\n\u003Cexample>\r\n\r\n## Example dialogue\r\n\r\n> **Dev:** \"How do I test the **sync service** without Docker?\"\r\n\r\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**.\"\r\n\r\n> **Dev:** \"So **sync-in** still creates a **bundle** and unpacks it?\"\r\n\r\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.\"\r\n\r\n\u003C\u002Fexample>\r\n\r\n## Re-running\r\n\r\nWhen invoked again in the same conversation:\r\n\r\n1. Read the existing `UBIQUITOUS_LANGUAGE.md`\r\n2. Incorporate any new terms from subsequent discussion\r\n3. Update definitions if understanding has evolved\r\n4. Re-flag any new ambiguities\r\n5. Rewrite the example dialogue to incorporate new terms\r\n",{"name":5,"description":7,"disable-model-invocation":24},true,"master","71bd1fbce5f3baf30a23044e9affdf43a8507d0d","docs\u002Freferences\u002Fagents\u002Fskills\u002Fubiquitous-language",0,"https:\u002F\u002Fgithub.com\u002Fsachahjkl\u002Fdw","https:\u002F\u002Fsachahjkl.github.io\u002Fdw\u002F","https:\u002F\u002Fgithub.com\u002Fsachahjkl","sacha.house","2026-11-10 20:39:20",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":24},[36,39,42],{"tool":37,"command":38},"npx","npx skills add sachahjkl\u002Fdw --skill ubiquitous-language",{"tool":40,"command":41},"bunx","bunx skills add sachahjkl\u002Fdw --skill ubiquitous-language",{"tool":43,"command":44},"pnpm","pnpm dlx skills add sachahjkl\u002Fdw --skill ubiquitous-language","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsachahjkl\u002Fdw\u002Fblob\u002Fmaster\u002Fdocs\u002Freferences\u002Fagents\u002Fskills\u002Fubiquitous-language\u002FSKILL.md",[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M75YB7ZBE0MH5JB6NPA9RNQ7","tooling-pnpm","Node tooling, pnpm, npm, worktree. Use when installing dependencies or running package-manager commands in a JS\u002FTS project and pnpm is available on the machine, especially with multiple worktrees.","https:\u002F\u002Fgithub.com\u002Fsachahjkl\u002Fdw\u002Fblob\u002Fmaster\u002Fdocs\u002Freferences\u002Fagents\u002Fskills\u002Ftooling-pnpm\u002FSKILL.md",[],[],{"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},"01M75YB6713YR2SM0XPEF2YMZ4","teach","Teach the user a new skill or concept, within this workspace.","https:\u002F\u002Fgithub.com\u002Fsachahjkl\u002Fdw\u002Fblob\u002Fmaster\u002Fdocs\u002Freferences\u002Fagents\u002Fskills\u002Fteach\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},"01M75YB4MZRJTAZDK45E87PMJT","sqlserver","SQL Server guidance. Use for Dapper queries, mappings, SQL-backed read\u002Fwrite flows.","https:\u002F\u002Fgithub.com\u002Fsachahjkl\u002Fdw\u002Fblob\u002Fmaster\u002Fdocs\u002Freferences\u002Fagents\u002Fskills\u002Fsqlserver\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},"01M75YB2280GKR9AR0XYDT6TSC","minimal-api-file-upload","File upload endpoints in ASP.NET minimal APIs (.NET 8+)","https:\u002F\u002Fgithub.com\u002Fsachahjkl\u002Fdw\u002Fblob\u002Fmaster\u002Fdocs\u002Freferences\u002Fagents\u002Fskills\u002Fminimal-api-file-upload\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},"01M75YAZXANWWQK564ZTRXD4HS","grill-me","Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions \"grill me\".","https:\u002F\u002Fgithub.com\u002Fsachahjkl\u002Fdw\u002Fblob\u002Fmaster\u002Fdocs\u002Freferences\u002Fagents\u002Fskills\u002Fgrill-me\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},"01M75YAVQ3SSWXEX5NPA8GVZ23","find-skills","Helps users discover and install agent skills when they ask questions like \"how do I do X\", \"find a skill for X\", \"is there a skill that can...\", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.","https:\u002F\u002Fgithub.com\u002Fsachahjkl\u002Fdw\u002Fblob\u002Fmaster\u002Fdocs\u002Freferences\u002Fagents\u002Fskills\u002Ffind-skills\u002FSKILL.md",[],[]]