- name
SKILL.md
File skill tetap berada di repositori penerbit.
Tempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill i18n-parity -a cursor -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill i18n-parity -a claude-code -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill i18n-parity -a codex -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill i18n-parity -a grok -yKirim pesan yang disalin di chat Grok Bot. Bot mengambil SKILL.md ini dari GitHub dan menambahkannya ke skill yang dipakai bersama oleh semua Bot Anda.
Install this skill: https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/HEAD/.codex/skills/i18n-parityDari penerbit
Mirror. The canonical copy of this skill — and the
i18n-audit.shscript it tells you to run — live at.claude/skills/i18n-parity/. Keep the two in sync; edit the canonical copy first.
This repository is localized on five independent surfaces, each with its own mechanism. A change that lands on one and not the others leaves the product half-translated: the English falls through, and the gap is invisible to anyone working in English. This skill states the invariant, maps every surface to the exact files, and gives one command that proves parity.
The invariant: English is the source of truth on every surface, and no change is done until every supported language carries it in the same PR. A fallback to English is a safety net, never a completed translation.
Supported languages are declared in one place — supportedLngs in
client/src/i18n/index.ts. Today:
en, zh, vi, ko, es. Everything below derives from that list; the
audit script reads it rather than hard-coding.
Verified against the tree — do not go looking for translation hooks in these, and do not add them without being asked:
index.html has no i18n layer. Do not add
data-lang markup; put localized long-form content in the wiki instead. Its
one language-aware element is the Languages (en/zh/…) stat label, which just
enumerates the codes.README.md is a concise English-only entry
point. It links every complete language guide but is not itself mirrored.
Full technical content belongs in README-EN.md and its four translations.client/index.html is an English shell: <html lang="en">,
og:locale=en_US, and English <title>/meta. The React app never reassigns
document.documentElement.lang when the user switches language — a known gap,
not something a translation PR is expected to fix.bin/ccam.js + cli/), the MCP server (mcp/), the Express server
(server/), the desktop shell (desktop/), the VS Code extension, and the
statusline contain no i18n wiring at all. Their output is English.client/src/lib/event-summary.ts and event-grouping.ts build tool-event
headlines and bullets from English template literals (Last message: …,
3 lines stdout, 2 matches). Their MODULE_GUIDE boilerplate claims strings
belong in i18n JSON, but neither file imports i18next. They sit outside the
key system today; do not "fix" them as part of a localization change.format.ts
helpers are used. Most components call toLocaleString() /
toLocaleString(undefined, …) directly, which follows the browser locale
rather than the chosen UI language. In new code prefer getCurrentLocale()
from format.ts; leave existing call sites alone unless asked.Find what you touched in the left column and ship everything in the right column in the same PR.
This is a large, exact, mechanical change. Read
references/new-language-checklist.md
and work through it top to bottom — it lists every file, in dependency order,
with the exact edit for each.
The three things contributors most often ship incomplete, stated up front:
README-<XX>.md is a full mirror of
README-EN.md — every section, every table row, every code block, every mermaid
diagram, in the same order. Do not summarize, do not drop "less important"
sections, do not stop halfway. Diff the heading list against README-EN.md
before you open the PR — the audit script compares heading counts, which
catches a truncated mirror but not a reordered or silently condensed one.<xx> bundle in wiki/i18n-content.js (thousands of body strings), a
full <xx> block in T, META, and every entry of ATTRIBUTE_TRANSLATIONS
in wiki/script.js. A locale that only fills T renders a page with
translated headings over English paragraphs, which is worse than English.Never translate: code inside <code>/backticks, commands, file and directory
paths, URLs, env-var names, HTTP methods and status codes, CLI flags, code
identifiers, numbers with units, brand and product names (Claude Code, MCP,
Codex), Claude Code hook event names (PreToolUse, Stop, …), and Claude
Code tool names (Bash, Agent, Read, Edit). Translate only the prose
around them. A block that is entirely code or identifiers needs no wiki
entry — it correctly falls back to English.
Two different things are spelled Agent. The Claude Code tool named
Agent (alongside Bash, Read, Edit) is an identifier and stays literal in
every locale, everywhere it appears — hook-event tables, tool lists, event
names. The UI noun for an agent (common:agent / common:subagent) is
product vocabulary with a per-locale contract, and only that noun has the
Spanish exception below. Never carry the exception into the tool name.
The UI noun's contract, asserted by client/src/i18n/__tests__/i18n.test.ts:
zh, vi, and ko keep Agent / Subagent literal; es renders them
agente / subagente. A new locale must decide this explicitly and add its
row to that test.
Terminology, per-locale conventions, and the shared glossary live in
references/translation-style.md. Read it
before translating; drifting terminology across pages is the most common
review comment on localization PRs.
client/tests/wiki-i18n.test.ts parses wiki/script.js by exact source
markers. It slices the file between literal strings — " const T = " …
"\n\n const PLAIN", " const ATTRIBUTE_TRANSLATIONS = " …
"\n const ATTR", " const META = " … "\n const trH" — and evals
what it finds. Renaming, reordering, or re-indenting those declarations
breaks the test with a confusing error. Add locales inside the existing
objects; leave the declaration lines alone.localStorage["wiki-lang"], not a URL
parameter. There is no ?lang= support. First visit falls back to a
navigator.language prefix ladder in wiki/script.js. To preview a locale,
use the switcher, or run
localStorage.setItem("wiki-lang", "<xx>") in the console and reload.The canonical copy — and both scripts — live at .claude/skills/i18n-parity/.
It is mirrored, with links rewritten to repo-root-relative paths and an
agents/openai.yaml interface added, to:
.agents/skills/i18n-parity/ (the shared/OpenAI skill tree).codex/skills/i18n-parity/ (Codex)Editing this skill means regenerating the mirrors — edit the canonical copy, then run:
bash .claude/skills/i18n-parity/scripts/sync-agent-mirrors.sh
i18n-audit.sh runs that script in --check mode, so a stale mirror is a
reported gap rather than silent drift. The mirrors carry no scripts: they point
back at the canonical ones by repo-root path.
# 1. Cross-surface parity: locale sets, namespace files, key parity, switcher
# entries, wiki bundles, full-guide mirrors and cross-links, agent-skill mirrors.
bash .claude/skills/i18n-parity/scripts/i18n-audit.sh
# 2. UI key/type/interpolation parity + locale formatting
npm run test:client
# 3. Wiki live-DOM coverage, inline tags, metadata, cache versions
cd client && npx vitest run tests/wiki-i18n.test.ts && cd ..
# 4. Documented counts asserted against the source tree
npm run test:server
# 5. The static wiki files and locale JSON are Prettier-managed
npm run format
i18n-audit.sh exits non-zero and names the exact file and locale for every
gap. Every check is a structural one — a named thing is present or it is not —
with a single exception: the wiki/i18n-content.js bundle-size check is a
stub detector (it flags a locale holding under 60% of the largest bundle's
entries). Exact per-string wiki coverage is asserted by
client/tests/wiki-i18n.test.ts, which walks the live DOM.
State explicitly which surfaces you updated and which you intentionally skipped
(with the reason), per the repo's verification policy in CLAUDE.md.
grep -rn "<neighbouring English text>" client/src/i18n/locales/en wiki/i18n-content.js wiki/script.js.CACHE_NAME / ?v= bump means
returning visitors never see the translation you just shipped.MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, full mirrored guides, locale-aware formatting, language
---name: i18n-paritydescription: MANDATORY for every coding agent and contributor touching localized content — keep all five localization…---# .codex/skills/i18n-parity/SKILL.mdRingkasan umum
MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, full mirrored guides, 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-EN.md or a localized guide, edit wiki/index.html, or add a language surface.
FAQ
Unduh .codex/skills/i18n-parity/SKILL.md dari penerbit, atau salin path-nya dan buka repositori. PlugMCP hanya mendaftar skill ini dan tidak meng-host filenya.
Penerbit menyimpannya di https://github.com/hoangsonww/Claude-Code-Agent-Monitor.
Claude, Cursor, Codex, dan Grok Build bisa membaca SKILL.md yang Anda tambahkan dari repositori penerbit. Grok Bot memasangnya saat Anda mengirim tautan folder GitHub skill tersebut di chat.
Run the update-project-docs (.claude/skills/update-project-docs/SKILL.md) skill — it owns the change→docs mapping — then come back here for the translation propagation it triggers. |
| Changed a documented count (plugins, skills, namespaces, languages) | The count can appear in the landing README, all five full guides, ARCHITECTURE.md, docs/*.md, index.html, wiki/index.html, wiki/i18n-content.js, and server/__tests__/plugins-marketplace.test.js. Grep the old number repo-wide; update every hit. |