[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASWTS02S2MBVMJR5XZRFFZ":3,"skill-same:01M7ASWTS02S2MBVMJR5XZRFFZ":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":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":44},"01M7ASWTS02S2MBVMJR5XZRFFZ","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\".","Diffusity\u002FrepoSphere_java_backend","Diffusity","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F119410541?v=4","01M7ASS8Z2BQV85KY5WA3C6G5E","Parth Maharaja","01M7ASS8ZRRXZNDAY7F88NBB4N",0,"MIT","https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fubiquitous-language\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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,"main","7623da0074c7f2756326dd104a40d1b0861a7edf",".agents\u002Fskills\u002Fubiquitous-language","https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend","https:\u002F\u002Fgithub.com\u002FDiffusity","Member @gdg-da | @ossdaiict ","2026-08-18 17:58:04",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Diffusity\u002FrepoSphere_java_backend --skill ubiquitous-language",{"tool":38,"command":39},"bunx","bunx skills add Diffusity\u002FrepoSphere_java_backend --skill ubiquitous-language",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Diffusity\u002FrepoSphere_java_backend --skill ubiquitous-language","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fubiquitous-language\u002FSKILL.md",[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",151,"https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fubiquitous-language\u002Fagents\u002Fopenai.yaml",[52,59,66,73,80,87],{"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},"01M7ASXG7ZJ4SX5JDCYSQFWBNG","writing-shape","Writing, exploit — shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7ASXCE1RQCW502FDAJZ7J3X","writing-great-skills","Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.","https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-great-skills\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7ASXA5NMS4ZEBCTWX29RNZ8","writing-fragments","Writing, explore — mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-fragments\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7ASX7AM9T3DAJ6A0A6GYTFZ","writing-beats","Writing, exploit — assemble raw material into a journey of beats, grounding each term before a beat leans on it.","https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-beats\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7ASX2F6FY5EW9SHSV5X2DHC","wizard","Generate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each step, and writing .env files and GitHub Actions secrets.","https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7ASWY2DYFMW5PK6X6YWCC90","wayfinder","Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002FDiffusity\u002FrepoSphere_java_backend\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]