[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0S7AP1BGCWP22ZFPSQWCH":3,"skill-same:01M7F0S7AP1BGCWP22ZFPSQWCH":60},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7F0S7AP1BGCWP22ZFPSQWCH","i18n-parity",null,"MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, mirrored READMEs, locale-aware formatting, language switchers) in parity across every supported language. Use automatically (without being asked) whenever you add or change user-visible UI copy, add an i18n key, edit README.md, edit wiki\u002Findex.html, or change docs that the READMEs and wiki mirror — and use the full new-language checklist whenever adding a language (a new README-XX.md, a new client\u002Fsrc\u002Fi18n\u002Flocales\u002F\u003Cxx>\u002F directory, or a new lang-option in the wiki).","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fi18n-parity-Claude-Code-Agent-Monitor\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: i18n-parity\ndescription: MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, mirrored READMEs, locale-aware formatting, language switchers) in parity across every supported language. Use automatically (without being asked) whenever you add or change user-visible UI copy, add an i18n key, edit README.md, edit wiki\u002Findex.html, or change docs that the READMEs and wiki mirror — and use the full new-language checklist whenever adding a language (a new README-XX.md, a new client\u002Fsrc\u002Fi18n\u002Flocales\u002F\u003Cxx>\u002F directory, or a new lang-option in the wiki).\n---\n\n> **Mirror.** The canonical copy of this skill — and the `i18n-audit.sh`\n> script it tells you to run — live at `.claude\u002Fskills\u002Fi18n-parity\u002F`.\n> Keep the two in sync; edit the canonical copy first.\n\n# i18n Parity\n\nThis repository is localized on **five independent surfaces**, each with its own\nmechanism. A change that lands on one and not the others leaves the product\nhalf-translated: the English falls through, and the gap is invisible to anyone\nworking in English. This skill states the invariant, maps every surface to the\nexact files, and gives one command that proves parity.\n\n**The invariant: English is the source of truth on every surface, and no change\nis done until every supported language carries it in the same PR.** A fallback\nto English is a safety net, never a completed translation.\n\nSupported languages are declared in one place — `supportedLngs` in\n`client\u002Fsrc\u002Fi18n\u002Findex.ts`. Today:\n**`en`, `zh`, `vi`, `ko`, `es`**. Everything below derives from that list; the\naudit script reads it rather than hard-coding.\n\n## The five surfaces\n\n| # | Surface | English source of truth | Translations live in | Automated gate |\n|---|---|---|---|---|\n| 1 | **Dashboard UI** | `client\u002Fsrc\u002Fi18n\u002Flocales\u002Fen\u002F*.json` | `client\u002Fsrc\u002Fi18n\u002Flocales\u002F\u003Cxx>\u002F*.json` (same 15 namespaces) | `client\u002Fsrc\u002Fi18n\u002F__tests__\u002Fi18n.test.ts` — key, type, and interpolation-token parity |\n| 2 | **Wiki page** | English text in the `wiki\u002Findex.html` DOM | `wiki\u002Fscript.js` (`T`, `ATTRIBUTE_TRANSLATIONS`, `META`, `languageLabels`, the two language ladders) + `wiki\u002Fi18n-content.js` (`window.__WIKI_CONTENT_I18N`, both the body bundles and `plain`) | `client\u002Ftests\u002Fwiki-i18n.test.ts` — live-DOM prose coverage, inline-tag preservation, block-length budgets, asset-version sync |\n| 3 | **Mirrored READMEs** | `README.md` | `README-CN.md` (zh), `README-VN.md` (vi), `README-KO.md` (ko), `README-ES.md` (es) | partial — `scripts\u002Fi18n-audit.sh` (existence, heading count, cross-links) and `server\u002F__tests__\u002Fplugins-marketplace.test.js` (documented counts); prose parity is review-only |\n| 4 | **Language switchers** | — | `client\u002Fsrc\u002Fcomponents\u002FSidebar.tsx`, `client\u002Fsrc\u002Flib\u002FpaletteCommands.ts`, the two `.lang-select-menu` blocks in `wiki\u002Findex.html`, `nav.json` `languageNames` \u002F `languageShort` | `scripts\u002Fi18n-audit.sh` |\n| 5 | **Locale-aware formatting** | — | `client\u002Fsrc\u002Flib\u002Fformat.ts` (`SupportedLanguage` union, `getCurrentLanguage()` whitelist, `getCurrentLocale()` BCP-47 map) | `client\u002Fsrc\u002Flib\u002F__tests__\u002Fformat.test.ts` |\n\n### What is deliberately NOT localized\n\nVerified against the tree — do not go looking for translation hooks in these,\nand do not add them without being asked:\n\n- **The root landing page `index.html`** has no i18n layer. Do not add\n  `data-lang` markup; put localized long-form content in the wiki instead. Its\n  one language-aware element is the `Languages (en\u002Fzh\u002F…)` stat label, which just\n  enumerates the codes.\n- **`client\u002Findex.html`** is an English shell: `\u003Chtml lang=\"en\">`,\n  `og:locale=en_US`, and English `\u003Ctitle>`\u002Fmeta. The React app never reassigns\n  `document.documentElement.lang` when the user switches language — a known gap,\n  not something a translation PR is expected to fix.\n- **The CLI (`bin\u002Fccam.js`), the MCP server (`mcp\u002F`), the Express server\n  (`server\u002F`), the desktop shell (`desktop\u002F`), the VS Code extension, and the\n  statusline** contain no i18n wiring at all. Their output is English.\n- **`client\u002Fsrc\u002Flib\u002Fevent-summary.ts` and `event-grouping.ts`** build tool-event\n  headlines and bullets from English template literals (`Last message: …`,\n  `3 lines stdout`, `2 matches`). Their MODULE_GUIDE boilerplate claims strings\n  belong in i18n JSON, but neither file imports i18next. They sit outside the\n  key system today; do not \"fix\" them as part of a localization change.\n- **Number and date formatting is only locale-aware where the `format.ts`\n  helpers are used.** Most components call `toLocaleString()` \u002F \n  `toLocaleString(undefined, …)` directly, which follows the *browser* locale\n  rather than the chosen UI language. In new code prefer `getCurrentLocale()`\n  from `format.ts`; leave existing call sites alone unless asked.\n\n## Workflow A — you changed content (the common case)\n\nFind what you touched in the left column and ship everything in the right column\n**in the same PR**.\n\n| You changed | You must also do |\n|---|---|\n| Added\u002Frenamed a UI string or i18n key | Add the key to `en` **and every other locale** in the same namespace file. Same key path, same value type, same `{{interpolation}}` tokens. |\n| Added a new namespace (new `*.json`) | Create it for every locale, then register the imports, the `resources` entry per language, and the `ns` array in `client\u002Fsrc\u002Fi18n\u002Findex.ts`. |\n| Added user-visible wiki text in `wiki\u002Findex.html` | Follow `.claude\u002Frules\u002Fwiki-i18n.md`: scannable layer (the `PLAIN` selector set — `.logo-sub`, `.section-label`, `.nav-section`, `.nav-empty`, `.stat-label`, `.t-label`, `h2`\u002F`h3`\u002F`h4`, `th`, `.hero-desc`, plus `.nav-link` \u002F `.hero-badge` trailing text nodes) → `T` in `wiki\u002Fscript.js`; body prose (the `HTML_SEL` set — `p`, `li`, `td`, `th`, captions, `.callout-body > strong`, `.route-desc`, footer) → `wiki\u002Fi18n-content.js` keyed by whitespace-normalized `innerHTML`; new `alt`\u002F`aria-label`\u002F`title`\u002F`placeholder` → `ATTRIBUTE_TRANSLATIONS`. Then bump `CACHE_NAME` in `wiki\u002Fsw.js` and the matching `?v=` query strings. |\n| Edited a section of `README.md` | Mirror the **same** edit at the corresponding section of `README-CN.md`, `README-VN.md`, `README-KO.md`, and `README-ES.md`. All four, every time. |\n| Changed behavior that the README\u002Fwiki document (env var, event type, route, CLI command, feature) | Run the `update-project-docs` (`.claude\u002Fskills\u002Fupdate-project-docs\u002FSKILL.md`) skill — it owns the change→docs mapping — then come back here for the translation propagation it triggers. |\n| Changed a documented count (plugins, skills, namespaces, languages) | The count is repeated across all five READMEs, `ARCHITECTURE.md`, `docs\u002F*.md`, `index.html`, `wiki\u002Findex.html`, `wiki\u002Fi18n-content.js`, and asserted in `server\u002F__tests__\u002Fplugins-marketplace.test.js`. Grep the old number repo-wide; update every hit. |\n\n## Workflow B — adding a new language\n\nThis is a large, exact, mechanical change. **Read\n[`references\u002Fnew-language-checklist.md`](references\u002Fnew-language-checklist.md)\nand work through it top to bottom** — it lists every file, in dependency order,\nwith the exact edit for each.\n\nThe three things contributors most often ship incomplete, stated up front:\n\n1. **The README mirror must be complete.** `README-\u003CXX>.md` is a full mirror of\n   `README.md` — every section, every table row, every code block, every mermaid\n   diagram, in the same order. Do not summarize, do not drop \"less important\"\n   sections, do not stop halfway. Diff the heading list against `README.md`\n   before you open the PR — the audit script compares heading counts, which\n   catches a truncated mirror but not a reordered or silently condensed one.\n2. **Every app key must be translated.** All 15 namespaces × every key. The\n   parity test fails on a missing key, but it *passes* on a key you copied over\n   in English — so read your diff for untranslated leftovers.\n3. **The wiki must be translated completely**, not just the headings. That means\n   a full `\u003Cxx>` bundle in `wiki\u002Fi18n-content.js` (thousands of body strings), a\n   full `\u003Cxx>` block in `T`, `META`, and every entry of `ATTRIBUTE_TRANSLATIONS`\n   in `wiki\u002Fscript.js`. A locale that only fills `T` renders a page with\n   translated headings over English paragraphs, which is worse than English.\n\n## What stays in English (all surfaces)\n\nNever translate: code inside `\u003Ccode>`\u002Fbackticks, commands, file and directory\npaths, URLs, env-var names, HTTP methods and status codes, CLI flags, code\nidentifiers, numbers with units, brand and product names (`Claude Code`, `MCP`,\n`Codex`), Claude Code hook event names (`PreToolUse`, `Stop`, …), and Claude\nCode tool names (`Bash`, `Agent`, `Read`, `Edit`). Translate only the prose\naround them. A block that is *entirely* code or identifiers needs no wiki\nentry — it correctly falls back to English.\n\n**Two different things are spelled `Agent`.** The Claude Code **tool** named\n`Agent` (alongside `Bash`, `Read`, `Edit`) is an identifier and stays literal in\n**every** locale, everywhere it appears — hook-event tables, tool lists, event\nnames. The **UI noun** for an agent (`common:agent` \u002F `common:subagent`) is\nproduct vocabulary with a per-locale contract, and only that noun has the\nSpanish exception below. Never carry the exception into the tool name.\n\nThe UI noun's contract, asserted by `client\u002Fsrc\u002Fi18n\u002F__tests__\u002Fi18n.test.ts`:\n`zh`, `vi`, and `ko` keep `Agent` \u002F `Subagent` literal; `es` renders them\n`agente` \u002F `subagente`. A new locale must decide this explicitly and add its\nrow to that test.\n\nTerminology, per-locale conventions, and the shared glossary live in\n[`references\u002Ftranslation-style.md`](references\u002Ftranslation-style.md). Read it\nbefore translating; drifting terminology across pages is the most common\nreview comment on localization PRs.\n\n## Two traps worth knowing before you edit the wiki\n\n1. **`client\u002Ftests\u002Fwiki-i18n.test.ts` parses `wiki\u002Fscript.js` by exact source\n   markers.** It slices the file between literal strings — `\"  const T = \"` …\n   `\"\\n\\n  const PLAIN\"`, `\"  const ATTRIBUTE_TRANSLATIONS = \"` …\n   `\"\\n  const ATTR\"`, `\"  const META = \"` … `\"\\n  const trH\"` — and `eval`s\n   what it finds. Renaming, reordering, or re-indenting those declarations\n   breaks the test with a confusing error. Add locales *inside* the existing\n   objects; leave the declaration lines alone.\n2. **The wiki's chosen language lives in `localStorage[\"wiki-lang\"]`, not a URL\n   parameter.** There is no `?lang=` support. First visit falls back to a\n   `navigator.language` prefix ladder in `wiki\u002Fscript.js`. To preview a locale,\n   use the switcher, or run\n   `localStorage.setItem(\"wiki-lang\", \"\u003Cxx>\")` in the console and reload.\n\n## This skill is mirrored for every agent\n\nThe canonical copy — and both scripts — live at `.claude\u002Fskills\u002Fi18n-parity\u002F`.\nIt is mirrored, with links rewritten to repo-root-relative paths and an\n`agents\u002Fopenai.yaml` interface added, to:\n\n- `.agents\u002Fskills\u002Fi18n-parity\u002F` (the shared\u002FOpenAI skill tree)\n- `.codex\u002Fskills\u002Fi18n-parity\u002F` (Codex)\n\n**Editing this skill means regenerating the mirrors** — edit the canonical copy,\nthen run:\n\n```bash\nbash .claude\u002Fskills\u002Fi18n-parity\u002Fscripts\u002Fsync-agent-mirrors.sh\n```\n\n`i18n-audit.sh` runs that script in `--check` mode, so a stale mirror is a\nreported gap rather than silent drift. The mirrors carry no scripts: they point\nback at the canonical ones by repo-root path.\n\n## Verify (do not skip)\n\n```bash\n# 1. Cross-surface parity: locale sets, namespace files, key parity, switcher\n#    entries, wiki bundles, README mirrors and cross-links, agent-skill mirrors.\nbash .claude\u002Fskills\u002Fi18n-parity\u002Fscripts\u002Fi18n-audit.sh\n\n# 2. UI key\u002Ftype\u002Finterpolation parity + locale formatting\nnpm run test:client\n\n# 3. Wiki live-DOM coverage, inline tags, metadata, cache versions\ncd client && npx vitest run tests\u002Fwiki-i18n.test.ts && cd ..\n\n# 4. Documented counts asserted against the source tree\nnpm run test:server\n\n# 5. The static wiki files and locale JSON are Prettier-managed\nnpm run format\n```\n\n`i18n-audit.sh` exits non-zero and names the exact file and locale for every\ngap. Every check is a structural one — a named thing is present or it is not —\nwith a single exception: the `wiki\u002Fi18n-content.js` bundle-size check is a\n**stub detector** (it flags a locale holding under 60% of the largest bundle's\nentries). Exact per-string wiki coverage is asserted by\n`client\u002Ftests\u002Fwiki-i18n.test.ts`, which walks the live DOM.\n\nState explicitly which surfaces you updated and which you intentionally skipped\n(with the reason), per the repo's verification policy in `CLAUDE.md`.\n\n## Tips\n\n- **Write the English first and get it right**, on all surfaces, before\n  translating anything. Every other locale is derived from it; re-translating\n  because the English moved is the biggest waste in this workflow.\n- To find where a string already lives: `grep -rn \"\u003Cneighbouring English text>\"\n  client\u002Fsrc\u002Fi18n\u002Flocales\u002Fen wiki\u002Fi18n-content.js wiki\u002Fscript.js`.\n- When adding a language, one locale per subagent is fine for the *wiki body*\n  bundle (it is large), but keep the README mirror with a single author so the\n  section order and terminology stay coherent.\n- Wiki edits are cache-first: forgetting the `CACHE_NAME` \u002F `?v=` bump means\n  returning visitors never see the translation you just shipped.\n","> **Mirror.** The canonical copy of this skill — and the `i18n-audit.sh`\n> script it tells you to run — live at `.claude\u002Fskills\u002Fi18n-parity\u002F`.\n> Keep the two in sync; edit the canonical copy first.\n\n# i18n Parity\n\nThis repository is localized on **five independent surfaces**, each with its own\nmechanism. A change that lands on one and not the others leaves the product\nhalf-translated: the English falls through, and the gap is invisible to anyone\nworking in English. This skill states the invariant, maps every surface to the\nexact files, and gives one command that proves parity.\n\n**The invariant: English is the source of truth on every surface, and no change\nis done until every supported language carries it in the same PR.** A fallback\nto English is a safety net, never a completed translation.\n\nSupported languages are declared in one place — `supportedLngs` in\n`client\u002Fsrc\u002Fi18n\u002Findex.ts`. Today:\n**`en`, `zh`, `vi`, `ko`, `es`**. Everything below derives from that list; the\naudit script reads it rather than hard-coding.\n\n## The five surfaces\n\n| # | Surface | English source of truth | Translations live in | Automated gate |\n|---|---|---|---|---|\n| 1 | **Dashboard UI** | `client\u002Fsrc\u002Fi18n\u002Flocales\u002Fen\u002F*.json` | `client\u002Fsrc\u002Fi18n\u002Flocales\u002F\u003Cxx>\u002F*.json` (same 15 namespaces) | `client\u002Fsrc\u002Fi18n\u002F__tests__\u002Fi18n.test.ts` — key, type, and interpolation-token parity |\n| 2 | **Wiki page** | English text in the `wiki\u002Findex.html` DOM | `wiki\u002Fscript.js` (`T`, `ATTRIBUTE_TRANSLATIONS`, `META`, `languageLabels`, the two language ladders) + `wiki\u002Fi18n-content.js` (`window.__WIKI_CONTENT_I18N`, both the body bundles and `plain`) | `client\u002Ftests\u002Fwiki-i18n.test.ts` — live-DOM prose coverage, inline-tag preservation, block-length budgets, asset-version sync |\n| 3 | **Mirrored READMEs** | `README.md` | `README-CN.md` (zh), `README-VN.md` (vi), `README-KO.md` (ko), `README-ES.md` (es) | partial — `scripts\u002Fi18n-audit.sh` (existence, heading count, cross-links) and `server\u002F__tests__\u002Fplugins-marketplace.test.js` (documented counts); prose parity is review-only |\n| 4 | **Language switchers** | — | `client\u002Fsrc\u002Fcomponents\u002FSidebar.tsx`, `client\u002Fsrc\u002Flib\u002FpaletteCommands.ts`, the two `.lang-select-menu` blocks in `wiki\u002Findex.html`, `nav.json` `languageNames` \u002F `languageShort` | `scripts\u002Fi18n-audit.sh` |\n| 5 | **Locale-aware formatting** | — | `client\u002Fsrc\u002Flib\u002Fformat.ts` (`SupportedLanguage` union, `getCurrentLanguage()` whitelist, `getCurrentLocale()` BCP-47 map) | `client\u002Fsrc\u002Flib\u002F__tests__\u002Fformat.test.ts` |\n\n### What is deliberately NOT localized\n\nVerified against the tree — do not go looking for translation hooks in these,\nand do not add them without being asked:\n\n- **The root landing page `index.html`** has no i18n layer. Do not add\n  `data-lang` markup; put localized long-form content in the wiki instead. Its\n  one language-aware element is the `Languages (en\u002Fzh\u002F…)` stat label, which just\n  enumerates the codes.\n- **`client\u002Findex.html`** is an English shell: `\u003Chtml lang=\"en\">`,\n  `og:locale=en_US`, and English `\u003Ctitle>`\u002Fmeta. The React app never reassigns\n  `document.documentElement.lang` when the user switches language — a known gap,\n  not something a translation PR is expected to fix.\n- **The CLI (`bin\u002Fccam.js`), the MCP server (`mcp\u002F`), the Express server\n  (`server\u002F`), the desktop shell (`desktop\u002F`), the VS Code extension, and the\n  statusline** contain no i18n wiring at all. Their output is English.\n- **`client\u002Fsrc\u002Flib\u002Fevent-summary.ts` and `event-grouping.ts`** build tool-event\n  headlines and bullets from English template literals (`Last message: …`,\n  `3 lines stdout`, `2 matches`). Their MODULE_GUIDE boilerplate claims strings\n  belong in i18n JSON, but neither file imports i18next. They sit outside the\n  key system today; do not \"fix\" them as part of a localization change.\n- **Number and date formatting is only locale-aware where the `format.ts`\n  helpers are used.** Most components call `toLocaleString()` \u002F \n  `toLocaleString(undefined, …)` directly, which follows the *browser* locale\n  rather than the chosen UI language. In new code prefer `getCurrentLocale()`\n  from `format.ts`; leave existing call sites alone unless asked.\n\n## Workflow A — you changed content (the common case)\n\nFind what you touched in the left column and ship everything in the right column\n**in the same PR**.\n\n| You changed | You must also do |\n|---|---|\n| Added\u002Frenamed a UI string or i18n key | Add the key to `en` **and every other locale** in the same namespace file. Same key path, same value type, same `{{interpolation}}` tokens. |\n| Added a new namespace (new `*.json`) | Create it for every locale, then register the imports, the `resources` entry per language, and the `ns` array in `client\u002Fsrc\u002Fi18n\u002Findex.ts`. |\n| Added user-visible wiki text in `wiki\u002Findex.html` | Follow `.claude\u002Frules\u002Fwiki-i18n.md`: scannable layer (the `PLAIN` selector set — `.logo-sub`, `.section-label`, `.nav-section`, `.nav-empty`, `.stat-label`, `.t-label`, `h2`\u002F`h3`\u002F`h4`, `th`, `.hero-desc`, plus `.nav-link` \u002F `.hero-badge` trailing text nodes) → `T` in `wiki\u002Fscript.js`; body prose (the `HTML_SEL` set — `p`, `li`, `td`, `th`, captions, `.callout-body > strong`, `.route-desc`, footer) → `wiki\u002Fi18n-content.js` keyed by whitespace-normalized `innerHTML`; new `alt`\u002F`aria-label`\u002F`title`\u002F`placeholder` → `ATTRIBUTE_TRANSLATIONS`. Then bump `CACHE_NAME` in `wiki\u002Fsw.js` and the matching `?v=` query strings. |\n| Edited a section of `README.md` | Mirror the **same** edit at the corresponding section of `README-CN.md`, `README-VN.md`, `README-KO.md`, and `README-ES.md`. All four, every time. |\n| Changed behavior that the README\u002Fwiki document (env var, event type, route, CLI command, feature) | Run the `update-project-docs` (`.claude\u002Fskills\u002Fupdate-project-docs\u002FSKILL.md`) skill — it owns the change→docs mapping — then come back here for the translation propagation it triggers. |\n| Changed a documented count (plugins, skills, namespaces, languages) | The count is repeated across all five READMEs, `ARCHITECTURE.md`, `docs\u002F*.md`, `index.html`, `wiki\u002Findex.html`, `wiki\u002Fi18n-content.js`, and asserted in `server\u002F__tests__\u002Fplugins-marketplace.test.js`. Grep the old number repo-wide; update every hit. |\n\n## Workflow B — adding a new language\n\nThis is a large, exact, mechanical change. **Read\n[`references\u002Fnew-language-checklist.md`](references\u002Fnew-language-checklist.md)\nand work through it top to bottom** — it lists every file, in dependency order,\nwith the exact edit for each.\n\nThe three things contributors most often ship incomplete, stated up front:\n\n1. **The README mirror must be complete.** `README-\u003CXX>.md` is a full mirror of\n   `README.md` — every section, every table row, every code block, every mermaid\n   diagram, in the same order. Do not summarize, do not drop \"less important\"\n   sections, do not stop halfway. Diff the heading list against `README.md`\n   before you open the PR — the audit script compares heading counts, which\n   catches a truncated mirror but not a reordered or silently condensed one.\n2. **Every app key must be translated.** All 15 namespaces × every key. The\n   parity test fails on a missing key, but it *passes* on a key you copied over\n   in English — so read your diff for untranslated leftovers.\n3. **The wiki must be translated completely**, not just the headings. That means\n   a full `\u003Cxx>` bundle in `wiki\u002Fi18n-content.js` (thousands of body strings), a\n   full `\u003Cxx>` block in `T`, `META`, and every entry of `ATTRIBUTE_TRANSLATIONS`\n   in `wiki\u002Fscript.js`. A locale that only fills `T` renders a page with\n   translated headings over English paragraphs, which is worse than English.\n\n## What stays in English (all surfaces)\n\nNever translate: code inside `\u003Ccode>`\u002Fbackticks, commands, file and directory\npaths, URLs, env-var names, HTTP methods and status codes, CLI flags, code\nidentifiers, numbers with units, brand and product names (`Claude Code`, `MCP`,\n`Codex`), Claude Code hook event names (`PreToolUse`, `Stop`, …), and Claude\nCode tool names (`Bash`, `Agent`, `Read`, `Edit`). Translate only the prose\naround them. A block that is *entirely* code or identifiers needs no wiki\nentry — it correctly falls back to English.\n\n**Two different things are spelled `Agent`.** The Claude Code **tool** named\n`Agent` (alongside `Bash`, `Read`, `Edit`) is an identifier and stays literal in\n**every** locale, everywhere it appears — hook-event tables, tool lists, event\nnames. The **UI noun** for an agent (`common:agent` \u002F `common:subagent`) is\nproduct vocabulary with a per-locale contract, and only that noun has the\nSpanish exception below. Never carry the exception into the tool name.\n\nThe UI noun's contract, asserted by `client\u002Fsrc\u002Fi18n\u002F__tests__\u002Fi18n.test.ts`:\n`zh`, `vi`, and `ko` keep `Agent` \u002F `Subagent` literal; `es` renders them\n`agente` \u002F `subagente`. A new locale must decide this explicitly and add its\nrow to that test.\n\nTerminology, per-locale conventions, and the shared glossary live in\n[`references\u002Ftranslation-style.md`](references\u002Ftranslation-style.md). Read it\nbefore translating; drifting terminology across pages is the most common\nreview comment on localization PRs.\n\n## Two traps worth knowing before you edit the wiki\n\n1. **`client\u002Ftests\u002Fwiki-i18n.test.ts` parses `wiki\u002Fscript.js` by exact source\n   markers.** It slices the file between literal strings — `\"  const T = \"` …\n   `\"\\n\\n  const PLAIN\"`, `\"  const ATTRIBUTE_TRANSLATIONS = \"` …\n   `\"\\n  const ATTR\"`, `\"  const META = \"` … `\"\\n  const trH\"` — and `eval`s\n   what it finds. Renaming, reordering, or re-indenting those declarations\n   breaks the test with a confusing error. Add locales *inside* the existing\n   objects; leave the declaration lines alone.\n2. **The wiki's chosen language lives in `localStorage[\"wiki-lang\"]`, not a URL\n   parameter.** There is no `?lang=` support. First visit falls back to a\n   `navigator.language` prefix ladder in `wiki\u002Fscript.js`. To preview a locale,\n   use the switcher, or run\n   `localStorage.setItem(\"wiki-lang\", \"\u003Cxx>\")` in the console and reload.\n\n## This skill is mirrored for every agent\n\nThe canonical copy — and both scripts — live at `.claude\u002Fskills\u002Fi18n-parity\u002F`.\nIt is mirrored, with links rewritten to repo-root-relative paths and an\n`agents\u002Fopenai.yaml` interface added, to:\n\n- `.agents\u002Fskills\u002Fi18n-parity\u002F` (the shared\u002FOpenAI skill tree)\n- `.codex\u002Fskills\u002Fi18n-parity\u002F` (Codex)\n\n**Editing this skill means regenerating the mirrors** — edit the canonical copy,\nthen run:\n\n```bash\nbash .claude\u002Fskills\u002Fi18n-parity\u002Fscripts\u002Fsync-agent-mirrors.sh\n```\n\n`i18n-audit.sh` runs that script in `--check` mode, so a stale mirror is a\nreported gap rather than silent drift. The mirrors carry no scripts: they point\nback at the canonical ones by repo-root path.\n\n## Verify (do not skip)\n\n```bash\n# 1. Cross-surface parity: locale sets, namespace files, key parity, switcher\n#    entries, wiki bundles, README mirrors and cross-links, agent-skill mirrors.\nbash .claude\u002Fskills\u002Fi18n-parity\u002Fscripts\u002Fi18n-audit.sh\n\n# 2. UI key\u002Ftype\u002Finterpolation parity + locale formatting\nnpm run test:client\n\n# 3. Wiki live-DOM coverage, inline tags, metadata, cache versions\ncd client && npx vitest run tests\u002Fwiki-i18n.test.ts && cd ..\n\n# 4. Documented counts asserted against the source tree\nnpm run test:server\n\n# 5. The static wiki files and locale JSON are Prettier-managed\nnpm run format\n```\n\n`i18n-audit.sh` exits non-zero and names the exact file and locale for every\ngap. Every check is a structural one — a named thing is present or it is not —\nwith a single exception: the `wiki\u002Fi18n-content.js` bundle-size check is a\n**stub detector** (it flags a locale holding under 60% of the largest bundle's\nentries). Exact per-string wiki coverage is asserted by\n`client\u002Ftests\u002Fwiki-i18n.test.ts`, which walks the live DOM.\n\nState explicitly which surfaces you updated and which you intentionally skipped\n(with the reason), per the repo's verification policy in `CLAUDE.md`.\n\n## Tips\n\n- **Write the English first and get it right**, on all surfaces, before\n  translating anything. Every other locale is derived from it; re-translating\n  because the English moved is the biggest waste in this workflow.\n- To find where a string already lives: `grep -rn \"\u003Cneighbouring English text>\"\n  client\u002Fsrc\u002Fi18n\u002Flocales\u002Fen wiki\u002Fi18n-content.js wiki\u002Fscript.js`.\n- When adding a language, one locale per subagent is fine for the *wiki body*\n  bundle (it is large), but keep the README mirror with a single author so the\n  section order and terminology stay coherent.\n- Wiki edits are cache-first: forgetting the `CACHE_NAME` \u002F `?v=` bump means\n  returning visitors never see the translation you just shipped.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fi18n-parity-Claude-Code-Agent-Monitor",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill i18n-parity",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill i18n-parity",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill i18n-parity","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fi18n-parity-Claude-Code-Agent-Monitor\u002FSKILL.md",true,[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",404,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fi18n-parity-Claude-Code-Agent-Monitor\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fnew-language-checklist.md",10540,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fi18n-parity-Claude-Code-Agent-Monitor\u002Freferences\u002Fnew-language-checklist.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Ftranslation-style.md",6437,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fi18n-parity-Claude-Code-Agent-Monitor\u002Freferences\u002Ftranslation-style.md",[61,68,73,80,87,94],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":69,"name":63,"nameZh":6,"description":64,"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},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\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},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\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},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\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},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]