[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M756R3CHWZP6F4XEYZAHD0E7":3,"skill-same:01M756R3CHWZP6F4XEYZAHD0E7":49},{"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":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M756R3CHWZP6F4XEYZAHD0E7","ubiquitous-language",null,"Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to .\u002Fdocs\u002Fubiquitous-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\". Forked from Matt Pocock's \"ubiquitous-language\" skill.","SoftwareAssassin2\u002FPlugins","SoftwareAssassin2","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F38842958?v=4","01M756NS55ARTH4KENH9HKVRNZ","01M756NS6B3QB1XR6QN6BPMR76",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2\u002FPlugins\u002Fblob\u002Fmain\u002Fplugins\u002Fubiquitous-language\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: ubiquitous-language\ndescription: Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to .\u002Fdocs\u002Fubiquitous-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\". Forked from Matt Pocock's \"ubiquitous-language\" skill.\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 `.\u002Fdocs\u002Fubiquitous-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 `.\u002Fdocs\u002Fubiquitous-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 `.\u002Fdocs\u002Fubiquitous-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 `.\u002Fdocs\u002Fubiquitous-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 `.\u002Fdocs\u002Fubiquitous-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 `.\u002Fdocs\u002Fubiquitous-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},"main","d01d9bbc815bb1c77bf61f24152dd84fca29ca41","plugins\u002Fubiquitous-language","https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2\u002FPlugins","https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2","2026-07-23 21:04:05",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add SoftwareAssassin2\u002FPlugins --skill ubiquitous-language",{"tool":35,"command":36},"bunx","bunx skills add SoftwareAssassin2\u002FPlugins --skill ubiquitous-language",{"tool":38,"command":39},"pnpm","pnpm dlx skills add SoftwareAssassin2\u002FPlugins --skill ubiquitous-language","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2\u002FPlugins\u002Fblob\u002Fmain\u002Fplugins\u002Fubiquitous-language\u002FSKILL.md",true,[43],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},".claude-plugin\u002Fplugin.json","REFERENCE","参考文档",342,"https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2\u002FPlugins\u002Fblob\u002Fmain\u002Fplugins\u002Fubiquitous-language\u002F.claude-plugin\u002Fplugin.json",[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M756R6NM9JCPKPDDEYYQ8756","wendy","Summon Wendy, a performance coach modeled on Wendy Rhoades from Billions, when the user invokes \u002Fwendy or asks for Wendy by name, or explicitly asks to get his head right — tilting, stalling, spiraling, avoiding, flat, or needing to lock in before a hard push. Wendy works the operator's state, never the plan. Do NOT use for feedback on strategies, plans, or decisions, and do not trigger uninvited.","https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2\u002FPlugins\u002Fblob\u002Fmain\u002Fplugins\u002Fwendy\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M756QYHCNZKH4EW9CGJPB4GT","tdd","Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions \"red-green-refactor\", wants integration tests, or asks for test-first development. Forked from Matt Pocock's \"tdd\" skill.","https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2\u002FPlugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M756QSQJ0WCP4HPW3SHBAFD5","voice","Speak Claude's responses aloud through the native OS voice (macOS `say`) — on demand via \u002Fspeak:speak (last response) or \u002Fspeak:specify (pick one), or automatically on every response via a toggleable Stop hook. Works locally on a Mac and, through a manually started host listener, from inside a Dev Container. Use when the user wants responses read aloud \u002F spoken \u002F voice output, wants auto-speak turned on or off, or asks whether the speak install is healthy.","https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2\u002FPlugins\u002Fblob\u002Fmain\u002Fplugins\u002Fspeak\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M756QGEMD1DF8YQ22FJ5DCAE","merge-request:review","Review a pull\u002Fmerge request (by id) or batch-review every open one against Chris's own engineering standards, staging high-signal findings to .data\u002Fmerge\u002F\u003CID>.md for later posting. Fetches head SHAs and applies the \"Reviewed at commit\" skip check BEFORE any checkout, resolves the head fork-safely, builds\u002Ftests it in a dedicated worktree, and treats a failing build\u002Fcheckout as the top blocking finding. First runs \u002Fdetect-source-control and hard-stops when the forge is unsupported. Use as \"review the PR\", \"review the open MRs\", \"any PRs need my eyes\", \"review \u003Cid>\".","https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2\u002FPlugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmerge-request\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M756Q7S9ABZSR6AT45GEDA9T","merge-request:post-findings","Take the findings staged by \u002Fmerge-request:review in .data\u002Fmerge\u002F\u003CID>.md and, with per-finding approval, post the approved ones to the forge as inline comments (general-comment fallback when a finding has no valid diff location) — or formally sign off a clean PR\u002FMR with a single \"Looks good.\" First runs \u002Fdetect-source-control and hard-stops when the forge is unsupported. Nothing reaches the forge except through the bundled scripts. Also runs a propose-then-confirm learned-preferences loop that teaches \u002Fmerge-request:review what you value (Don't-raise \u002F Wording \u002F Confirmed-valued), and records skipped findings to the artifact's","https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2\u002FPlugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmerge-request\u002Fskills\u002Fpost-findings\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M756PYDS6DPV9HMZ1CJCGX93","merge-request:fix","Monitor an open pull\u002Fmerge request (by id) and, as feedback arrives, gather every actionable item — human + bot\u002FAI review comments and MR-attributable CI failures — deduplicated against a durable ledger so nothing is handled twice. Polls on an adaptive scheduled-wakeup cadence until the PR\u002FMR closes. First runs \u002Fdetect-source-control and hard-stops when the forge is unsupported. Use as \"watch the PR\", \"monitor the MR for feedback\", \"fix review feedback on \u003Cid>\", or the continuation of \u002Fmerge-request:create.","https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2\u002FPlugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmerge-request\u002Fskills\u002Ffix\u002FSKILL.md",[],[]]