[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D2GRJ1MKMMEACKDFSAKF20":3,"skill-same:01M6D2GRJ1MKMMEACKDFSAKF20":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M6D2GRJ1MKMMEACKDFSAKF20","zudo-doc-translate",null,"Translate zudo-doc documentation between the locales configured in this project, with Japanese conventions applied only to the `ja` locale.","zudolab\u002Fzudo-doc","zudolab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F266356510?v=4","01M6D2E9N9X9851YB24CEQF04H","01M6D2E9SFKZ0FWBMPB2625H28",1,"MIT","https:\u002F\u002Fgithub.com\u002Fzudolab\u002Fzudo-doc\u002Fblob\u002Fmain\u002Fpackages\u002Fcreate-zudo-doc\u002Ftemplates\u002Ffeatures\u002FclaudeSkills\u002Ffiles\u002F.claude\u002Fskills\u002Fzudo-doc-translate\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30],"translate","doc","zudo doc translate","docs","documentation","translate docs","only","japanese","i18n","conventions","project","with","locale","2026-11-10 10:12:30",false,"---\nname: zudo-doc-translate\ndescription: Translate zudo-doc documentation between the locales configured in this project, with Japanese conventions applied only to the `ja` locale.\ntriggers:\n  - translate\n  - 翻訳\n  - i18n\n  - translate docs\n  - ドキュメント翻訳\n---\n\n# zudo-doc Translation Skill\n\nTranslate documentation between the locales configured in this project. Do not\nassume that a project has only English and Japanese content.\n\n## i18n Structure\n\nThis skill applies only when this project's i18n feature is enabled. A\nnon-i18n scaffold has no non-empty `locales` map in `zfb.config.ts` and no\nadditional-locale content directory — there is nothing to translate. Read the\n`zudoDoc({...})` call in `zfb.config.ts` before choosing any source or target:\n\n- `defaultLocale` identifies the default locale. Its content is in `docsDir`\n  (normally `src\u002Fcontent\u002Fdocs\u002F`) and its routes are unprefixed (`\u002Fdocs\u002F...`).\n- `locales` is the exact map of additional locale code → `{ label, dir }`.\n  Translate into every requested map entry at its configured `dir`, rather than\n  guessing a directory from the locale code.\n- Each configured additional locale is routed at `\u002F\u003Clocale-code>\u002Fdocs\u002F...`.\n\nNever discover current locales with a `src\u002Fcontent\u002Fdocs-*` glob. Versioned\ntrees such as `src\u002Fcontent\u002Fdocs-v1` or `src\u002Fcontent\u002Fdocs-v1-ja` are snapshots,\nnot current locale roots.\n\nThe scaffold's starter content is language-specific: the `ja` locale receives\nJapanese starter prose when it is configured, while arbitrary non-EN locales\nstart with English placeholder prose pending translation. Do not describe a\nnon-JA locale as already translated.\n\n## Translation Rules\n\n### Keep in English (do NOT translate)\n\n- Component names: `\u003CNote>`, `\u003CTip>`, `\u003CInfo>`, `\u003CWarning>`, `\u003CDanger>`, `\u003CTabs>`, `\u003CTabItem>`, `\u003CDetails>`\n- Code blocks — code is universal\n- File paths and configured directory names\n- CLI commands: `\u003Cpm> run dev`, `\u003Cpm> run build`, etc. (`\u003Cpm>` = this project's package manager)\n- Technical terms that are standard in English (e.g., component, props, frontmatter, slug)\n- Frontmatter field keys (`title`, `description`, `sidebar_position`, `category`)\n\n### Translate\n\n- Frontmatter field values (for example, the `title` and `description` values)\n- The `title` prop of admonition components (for example, `\u003CNote title=\"注意\">`)\n- Prose content, headings, list items, and table cells (except as noted below)\n\n### Japanese-only conventions\n\nApply these conventions only when the source or target locale code is `ja`:\n\n- In tables with a \"Required\" column, use **\"Yes\"** \u002F **\"No\"** directly,\n  rather than Japanese conversational yes\u002Fno.\n- Preserve the project's Japanese technical terminology and natural prose.\n\nFor every locale code other than `ja`, follow that language's conventions when\nknown; do not infer Japanese guidance or claim that its starter content is\ntranslated.\n\n### Internal links\n\nAdjust link paths when translating between locale trees:\n\n- Default → an additional locale: `\u002Fdocs\u002Fgetting-started` →\n  `\u002F\u003Clocale-code>\u002Fdocs\u002Fgetting-started`\n- An additional locale → default: `\u002F\u003Clocale-code>\u002Fdocs\u002Fgetting-started` →\n  `\u002Fdocs\u002Fgetting-started`\n- Between additional locales: replace the source locale prefix with the target\n  locale prefix.\n\n## File Naming\n\nEvery locale uses the same filenames. Only the configured parent directory\ndiffers. For example, a file under `src\u002Fcontent\u002Fdocs\u002Fguides\u002Fwriting-docs.mdx`\nmaps to the same relative path under the `dir` configured for the target\nlocale.\n\n## Workflow\n\n### Default → an additional locale\n\n1. Read the source file from the configured default `docsDir`.\n2. Read the corresponding target file under the target locale's configured\n   `dir`, if it exists. Use it as a base instead of overwriting it from scratch.\n3. Translate the content following the rules above. Apply Japanese conventions\n   only when the target locale code is `ja`.\n4. Create the target file at the equivalent relative path when it does not yet\n   exist.\n5. Verify internal links use the target locale prefix.\n\n### An additional locale → default\n\n1. Read the source file under that locale's configured `dir`.\n2. Read the corresponding file under the configured default `docsDir`, if it\n   exists; otherwise create it at the equivalent relative path.\n3. Translate the content and remove the source locale prefix from internal\n   links.\n\n### Between additional locales\n\nUse the exact `dir` entries from `locales` for both source and target. Preserve\nthe relative file path and code blocks, and replace the source route prefix\nwith the target route prefix. Japanese conventions apply only if one of those\nlocale codes is `ja`.\n\n## Post-Translation Checks\n\n- `defaultLocale`, `docsDir`, and every `locales` map entry are unchanged\n- Frontmatter keys are unchanged; only values are translated\n- All admonition component names remain in English\n- Code blocks are untouched\n- Internal links use the correct configured locale prefix\n- The target directory mirrors the source relative file structure\n","# zudo-doc Translation Skill\n\nTranslate documentation between the locales configured in this project. Do not\nassume that a project has only English and Japanese content.\n\n## i18n Structure\n\nThis skill applies only when this project's i18n feature is enabled. A\nnon-i18n scaffold has no non-empty `locales` map in `zfb.config.ts` and no\nadditional-locale content directory — there is nothing to translate. Read the\n`zudoDoc({...})` call in `zfb.config.ts` before choosing any source or target:\n\n- `defaultLocale` identifies the default locale. Its content is in `docsDir`\n  (normally `src\u002Fcontent\u002Fdocs\u002F`) and its routes are unprefixed (`\u002Fdocs\u002F...`).\n- `locales` is the exact map of additional locale code → `{ label, dir }`.\n  Translate into every requested map entry at its configured `dir`, rather than\n  guessing a directory from the locale code.\n- Each configured additional locale is routed at `\u002F\u003Clocale-code>\u002Fdocs\u002F...`.\n\nNever discover current locales with a `src\u002Fcontent\u002Fdocs-*` glob. Versioned\ntrees such as `src\u002Fcontent\u002Fdocs-v1` or `src\u002Fcontent\u002Fdocs-v1-ja` are snapshots,\nnot current locale roots.\n\nThe scaffold's starter content is language-specific: the `ja` locale receives\nJapanese starter prose when it is configured, while arbitrary non-EN locales\nstart with English placeholder prose pending translation. Do not describe a\nnon-JA locale as already translated.\n\n## Translation Rules\n\n### Keep in English (do NOT translate)\n\n- Component names: `\u003CNote>`, `\u003CTip>`, `\u003CInfo>`, `\u003CWarning>`, `\u003CDanger>`, `\u003CTabs>`, `\u003CTabItem>`, `\u003CDetails>`\n- Code blocks — code is universal\n- File paths and configured directory names\n- CLI commands: `\u003Cpm> run dev`, `\u003Cpm> run build`, etc. (`\u003Cpm>` = this project's package manager)\n- Technical terms that are standard in English (e.g., component, props, frontmatter, slug)\n- Frontmatter field keys (`title`, `description`, `sidebar_position`, `category`)\n\n### Translate\n\n- Frontmatter field values (for example, the `title` and `description` values)\n- The `title` prop of admonition components (for example, `\u003CNote title=\"注意\">`)\n- Prose content, headings, list items, and table cells (except as noted below)\n\n### Japanese-only conventions\n\nApply these conventions only when the source or target locale code is `ja`:\n\n- In tables with a \"Required\" column, use **\"Yes\"** \u002F **\"No\"** directly,\n  rather than Japanese conversational yes\u002Fno.\n- Preserve the project's Japanese technical terminology and natural prose.\n\nFor every locale code other than `ja`, follow that language's conventions when\nknown; do not infer Japanese guidance or claim that its starter content is\ntranslated.\n\n### Internal links\n\nAdjust link paths when translating between locale trees:\n\n- Default → an additional locale: `\u002Fdocs\u002Fgetting-started` →\n  `\u002F\u003Clocale-code>\u002Fdocs\u002Fgetting-started`\n- An additional locale → default: `\u002F\u003Clocale-code>\u002Fdocs\u002Fgetting-started` →\n  `\u002Fdocs\u002Fgetting-started`\n- Between additional locales: replace the source locale prefix with the target\n  locale prefix.\n\n## File Naming\n\nEvery locale uses the same filenames. Only the configured parent directory\ndiffers. For example, a file under `src\u002Fcontent\u002Fdocs\u002Fguides\u002Fwriting-docs.mdx`\nmaps to the same relative path under the `dir` configured for the target\nlocale.\n\n## Workflow\n\n### Default → an additional locale\n\n1. Read the source file from the configured default `docsDir`.\n2. Read the corresponding target file under the target locale's configured\n   `dir`, if it exists. Use it as a base instead of overwriting it from scratch.\n3. Translate the content following the rules above. Apply Japanese conventions\n   only when the target locale code is `ja`.\n4. Create the target file at the equivalent relative path when it does not yet\n   exist.\n5. Verify internal links use the target locale prefix.\n\n### An additional locale → default\n\n1. Read the source file under that locale's configured `dir`.\n2. Read the corresponding file under the configured default `docsDir`, if it\n   exists; otherwise create it at the equivalent relative path.\n3. Translate the content and remove the source locale prefix from internal\n   links.\n\n### Between additional locales\n\nUse the exact `dir` entries from `locales` for both source and target. Preserve\nthe relative file path and code blocks, and replace the source route prefix\nwith the target route prefix. Japanese conventions apply only if one of those\nlocale codes is `ja`.\n\n## Post-Translation Checks\n\n- `defaultLocale`, `docsDir`, and every `locales` map entry are unchanged\n- Frontmatter keys are unchanged; only values are translated\n- All admonition component names remain in English\n- Code blocks are untouched\n- Internal links use the correct configured locale prefix\n- The target directory mirrors the source relative file structure\n",{"name":5,"triggers":36,"description":7},[18,37,26,23,38],"翻訳","ドキュメント翻訳","main","81e0e97f6a11185202e63a647a55df3e0cffc50a","packages\u002Fcreate-zudo-doc\u002Ftemplates\u002Ffeatures\u002FclaudeSkills\u002Ffiles\u002F.claude\u002Fskills\u002Fzudo-doc-translate",0,"https:\u002F\u002Fgithub.com\u002Fzudolab\u002Fzudo-doc","https:\u002F\u002Fgithub.com\u002Fzudolab","2026-11-12 03:19:50",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add zudolab\u002Fzudo-doc --skill zudo-doc-translate",{"tool":52,"command":53},"bunx","bunx skills add zudolab\u002Fzudo-doc --skill zudo-doc-translate",{"tool":55,"command":56},"pnpm","pnpm dlx skills add zudolab\u002Fzudo-doc --skill zudo-doc-translate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzudolab\u002Fzudo-doc\u002Fblob\u002Fmain\u002Fpackages\u002Fcreate-zudo-doc\u002Ftemplates\u002Ffeatures\u002FclaudeSkills\u002Ffiles\u002F.claude\u002Fskills\u002Fzudo-doc-translate\u002FSKILL.md",true,[],[61,95,122,160,172,191],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":77,"publishedAt":31},"01M6D2GZKKY2E651Q297NEZEGV","zudo-doc-writing","Doc-writing and navigation-structure guide for this zudo-doc project. Consult BEFORE creating pages, adding categories, designing header navigation, or writing\u002Fediting mdx content under src\u002Fcontent\u002F. Covers: reading the AUTHORING.md editorial policy and its four placement questions, when to run a structure review, plan-the-nav-tree-first workflow, tree vs note-tray categories, the recommended 3-level hierarchy (header → sidebar → nested), filesystem navigation as the default, linked versus heading-only category rows, category index pages, sidebar_position discipline, frontmatter schema, no-h1 rule, relative .mdx links, and admonition syntax. Triggered by 'write docs', 'add a page', 'create a page', 'add category', 'structure navigation', 'nav design', 'zudo-doc-writing'.","https:\u002F\u002Fgithub.com\u002Fzudolab\u002Fzudo-doc\u002Fblob\u002Fmain\u002Fpackages\u002Fcreate-zudo-doc\u002Ftemplates\u002Ffeatures\u002FclaudeSkillsWriting\u002Ffiles\u002F.claude\u002Fskills\u002Fzudo-doc-writing\u002FSKILL.md",[67,72],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[78,79,19,28,80,81,24,82,83,84,85,86,87,88,89,90,91,92,93,94],"writing","zudo doc writing","default","design","workflow","consult","create","structure","plan","discipline","categories","when","review","hierarchy","filesystem navigation","run","src",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":31},"01M6D2GWFZ81SCB168Z4P4NYYN","zudo-doc-version-bump","Bump package version, update changelog and versioned docs snapshot (if those features are enabled), commit, tag, and create a GitHub release. Use when: (1) User says 'version bump', 'bump version', 'release', or 'zudo-doc-version-bump', (2) User wants to create a new release of this project.","https:\u002F\u002Fgithub.com\u002Fzudolab\u002Fzudo-doc\u002Fblob\u002Fmain\u002Fpackages\u002Fcreate-zudo-doc\u002Ftemplates\u002Ffeatures\u002FclaudeSkills\u002Ffiles\u002F.claude\u002Fskills\u002Fzudo-doc-version-bump\u002FSKILL.md",[],[102,103,104,105,19,28,106,107,108,109,110,84,111,112,113,114,115,116,21,117,118,119,89,120,121],"bump","zudo doc version bump","version","version bump","update changelog","package","use","patch","commit","changelog","github","update","release","snapshot","bump version","user","proposal","new","features","github release",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":137,"publishedAt":31},"01M6D2GMXQGVKJZTA35Q9AZN7V","zudo-doc-design-system","Project-specific CSS and component rules for zudo-doc. Must be consulted before writing or editing CSS, zudo-wind utilities, color tokens, or component markup in this project. Covers: component-first strategy, design token system, three-tier color architecture, and palette index convention. Triggered by 'design system', 'zudo-doc-design-system', 'zudo-doc-css-wisdom' (old name).","https:\u002F\u002Fgithub.com\u002Fzudolab\u002Fzudo-doc\u002Fblob\u002Fmain\u002Fpackages\u002Fcreate-zudo-doc\u002Ftemplates\u002Ffeatures\u002FclaudeSkills\u002Ffiles\u002F.claude\u002Fskills\u002Fzudo-doc-design-system\u002FSKILL.md",[128,131,134],{"categoryNo":129,"categoryName":130,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":132,"categoryName":133,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":135,"categoryName":136,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000032","设计师",[138,139,81,19,140,141,142,28,143,144,145,78,146,147,148,149,150,151,152,153,154,155,156,157,158,159],"zudo doc design system","system","design system","css","three","editing","tokens","strategy","wisdom","Rules","architecture","component","first","token","design-system","index","design token","wind","palette","Utilities","color","for",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":31},"01M6D2GJYJQRZTHVY1CN884E96","localized-shell","Fixture skill for localized generated resource routes.","https:\u002F\u002Fgithub.com\u002Fzudolab\u002Fzudo-doc\u002Fblob\u002Fmain\u002Fe2e\u002Ffixtures\u002Fi18n\u002Fsrc\u002Fcontent\u002Fresources\u002F.claude\u002Fskills\u002Flocalized-shell\u002FSKILL.md",[],[167,168,169,170,171,159],"localized shell","shell","fixture","generated","fixture skill",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":180,"publishedAt":31},"01M6D2GF8BK70Y7TE3B7NCX87H","zudo-doc-writing-rules","Doc-writing rules for zudo-doc content (mdx files under src\u002Fcontent\u002Fdocs\u002F and src\u002Fcontent\u002Fdocs-ja\u002F). Consult before writing or editing doc content. Covers: no h1 in content, sidebar_position is mandatory, kebab-case file names, bilingual rule, linking conventions, and admonition syntax. Triggered by 'writing rules', 'zudo-doc-writing-rules', 'doc rule', 'mdx rule', 'write a doc', 'create a page'.","https:\u002F\u002Fgithub.com\u002Fzudolab\u002Fzudo-doc\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fzudo-doc-writing-rules\u002FSKILL.md",[178,179],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},[181,19,78,147,79,182,84,183,143,94,184,185,27,186,187,83,159,188,189,190],"zudo doc writing rules","writing rules","page","write","syntax","files","file","true","case","linking",{"skillNo":192,"name":97,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":196,"publishedAt":31},"01M6D2GBRX65FV1FCMFYHPNNP4","Bump the lockstep monorepo version, author package-specific changelogs, commit, tag all three packages, and create distinct GitHub releases. Use when: (1) User says 'version bump', 'bump version', 'release', or 'zudo-doc-version-bump', (2) User wants to create a new release of this monorepo.","https:\u002F\u002Fgithub.com\u002Fzudolab\u002Fzudo-doc\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fzudo-doc-version-bump\u002FSKILL.md",[],[102,103,104,105,19,142,197,107,108,109,110,84,198,112,199,114,116,117,118,188,119,89,200],"monorepo","packages","releases","author"]