[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7856M3ZBQ66CVTS35STB5VB":3,"skill-same:01M7856M3ZBQ66CVTS35STB5VB":51},{"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":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M7856M3ZBQ66CVTS35STB5VB","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\".","mhrsdev\u002FAI-Agent-Skills-Library","mhrsdev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F297913466?v=4","01M784VR2WC3PFWGB33RB1EVF9","MHRS","01M784VR3WX1XAH7SX6R2QZ99R",7,"MIT","https:\u002F\u002Fgithub.com\u002Fmhrsdev\u002FAI-Agent-Skills-Library\u002Fblob\u002Fmain\u002Forganized-skills\u002Fknowledge-learning-writing\u002Fmattpocock-skills\u002Fskills\u002Fdeprecated\u002Fubiquitous-language\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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":24},true,"main","6d80f3aba1c1dd6c29729d8e3019577b9411126c","organized-skills\u002Fknowledge-learning-writing\u002Fmattpocock-skills\u002Fskills\u002Fdeprecated\u002Fubiquitous-language",0,"https:\u002F\u002Fgithub.com\u002Fmhrsdev\u002FAI-Agent-Skills-Library","https:\u002F\u002Fgithub.com\u002Fmhrsdev","2026-07-05 06:21:49",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add mhrsdev\u002FAI-Agent-Skills-Library --skill ubiquitous-language",{"tool":38,"command":39},"bunx","bunx skills add mhrsdev\u002FAI-Agent-Skills-Library --skill ubiquitous-language",{"tool":41,"command":42},"pnpm","pnpm dlx skills add mhrsdev\u002FAI-Agent-Skills-Library --skill ubiquitous-language","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmhrsdev\u002FAI-Agent-Skills-Library\u002Fblob\u002Fmain\u002Forganized-skills\u002Fknowledge-learning-writing\u002Fmattpocock-skills\u002Fskills\u002Fdeprecated\u002Fubiquitous-language\u002FSKILL.md",[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"README.md","REFERENCE","参考文档",2533,"https:\u002F\u002Fgithub.com\u002Fmhrsdev\u002FAI-Agent-Skills-Library\u002Fblob\u002Fmain\u002Forganized-skills\u002Fknowledge-learning-writing\u002Fmattpocock-skills\u002Fskills\u002Fdeprecated\u002Fubiquitous-language\u002FREADME.md",[52,59,65,72,79,86],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M785CANS10KGVX2B6JHZ2QX5","static-project-gallery-upload","Use when a user provides project\u002Fportfolio\u002Fgallery images for a static website and wants them displayed on the site, exact duplicate images removed, visually related building views kept together, images optimized, and a host upload folder such as \"UP FILE\" prepared. Triggers include Persian requests like \"عکس پروژه ها\", \"تکراری نباشن\", \"توی سایت نمایش داده بشن\", \"فایل های هاست\", \"UP FILE\".","https:\u002F\u002Fgithub.com\u002Fmhrsdev\u002FAI-Agent-Skills-Library\u002Fblob\u002Fmain\u002Forganized-skills\u002Fwebsite-business-builds\u002Fstatic-project-gallery-upload\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M785C3S56JQ75Y4QTPZWH9PG","contact-location-section","https:\u002F\u002Fgithub.com\u002Fmhrsdev\u002FAI-Agent-Skills-Library\u002Fblob\u002Fmain\u002Forganized-skills\u002Fwebsite-business-builds\u002Fcontact-location-section\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M785BWRPMZH26VQYVK3X4VY3","azerbaijan-website-build","Build premium tri-lingual websites from scratch for Azerbaijani businesses. Handles data gathering (website scrape, social media, or interview), brand development, and full Astro + Tailwind build with AZ\u002FRU\u002FEN language support.","https:\u002F\u002Fgithub.com\u002Fmhrsdev\u002FAI-Agent-Skills-Library\u002Fblob\u002Fmain\u002Forganized-skills\u002Fwebsite-business-builds\u002F07-azerbaijan-website-build\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M785BMQ7C9QPACPTVEPZ4C4X","local-business-rebuild","Build a stunning new website for a local business prospect. Adapted from the full website-rebuild skill but optimized for speculative local business pitches. 10-phase process: brand extraction, SEO audit, design audit, rebuild plan, full build with design system, copy optimization, combined QA, pre-deploy checklist, and output to monorepo. Uses scraped content from prospect-scrape as input. No tools\u002Fcalculator research phase. Single combined QA round. Triggers on: \"rebuild prospect\", \"local business rebuild\", \"build prospect site\", \"rebuild their site\", \"prospect rebuild\", or any request to build a new website for a qualified prospect.","https:\u002F\u002Fgithub.com\u002Fmhrsdev\u002FAI-Agent-Skills-Library\u002Fblob\u002Fmain\u002Forganized-skills\u002Fwebsite-business-builds\u002F06-local-business-rebuild\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M785BA38WMK2QEA9QBX3G201","website-rebuild","Full website rebuild agent. Takes an existing website URL and rebuilds it from scratch into a world-class, SEO-optimized, WCAG AA accessible, visually stunning website using Astro + Tailwind CSS, deployed to Vercel via GitHub. Executes a rigorous 14-phase process: brand extraction, content scraping, SEO audit, design audit, rebuild planning, full build with design system, copy optimization, 3 QA rounds, competitive tools research, tools build, tools QA, pre-deploy checklist, and Vercel deployment. Produces 11+ documentation deliverables. Triggers on: \"rebuild website\", \"redesign website\", \"rebuild site from URL\", \"website rebuild\", \"redo this website\", \"make this website better\", \"rebuild from scratch\", \"full site redesign\", or any request to take an existing URL and create a new, professional website from it. Also triggers when the user provides a URL and asks to build\u002Fcreate\u002Fdesign a new version of that site.","https:\u002F\u002Fgithub.com\u002Fmhrsdev\u002FAI-Agent-Skills-Library\u002Fblob\u002Fmain\u002Forganized-skills\u002Fwebsite-business-builds\u002F05-website-rebuild\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M785B6YDMSVJ30MTW6QDPME9","triage","Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002Fmhrsdev\u002FAI-Agent-Skills-Library\u002Fblob\u002Fmain\u002Forganized-skills\u002Fskill-authoring-meta\u002Ftriage\u002FSKILL.md",[],[]]