Skip to main content
rule CX Codex

i18n-parity — Claude Code rule: what it does, how to install

i18n-parity enforces identical localization coverage across all supported locales in the same pull request, preventing incomplete translations.

MIT ★ 1,198 updated 2026-10-23

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/rules/i18n-parity.md
Open on GitHub

What i18n-parity does

This rule stops coding agents from submitting partial translations. English serves as the single source of truth across the project. Whenever an agent creates a key in client/src/i18n/locales/en/<ns>.json, it must add the identical key path, value type, and interpolation tokens to every locale file in the same change. Edits to README-EN.md must be mirrored across README-CN.md, README-VN.md, README-KO.md, and README-ES.md.

Identifiers, CLI flags, URLs, environment variables, and Claude Code tool names like Bash, Agent, Read, and Edit remain untouched. The UI noun agent turns into agente in Spanish, while the tool name stays literal everywhere.

The canonical instructions live in .claude/skills/i18n-parity/. The check script bash .claude/skills/i18n-parity/scripts/i18n-audit.sh must return code 0, failing immediately whenever mirrors in .codex/ fall behind or a registered locale lacks translations.

What it helps with

  • Keep new localization keys synchronized across every supported language file
  • Mirror documentation updates from README-EN.md into all translated guides
  • Prevent translation of identifiers, command flags, and built-in agent tool names
  • Audit translation completeness before merging changes

Example prompts for the agent

  • Add a new key to client/src/i18n/locales/en/common.json and sync all locales following i18n-parity
  • Update the setup section in README-EN.md and mirror the changes to every localized guide
  • Run bash .claude/skills/i18n-parity/scripts/i18n-audit.sh and fix missing locale keys

How to install i18n-parity

Manually: put the files in place

.claude/rules/i18n-parity.md

The paths frontmatter field limits the files

Step by step, with commands for each platform: AGENTS.md vs CLAUDE.md: what they are and which one to use

Questions about i18n-parity

How to install i18n-parity in Claude Code?

Save the rule file to .claude/rules/i18n-parity.md in your project root.

What does the i18n-parity rule do?

It requires coding agents to mirror interface text and documentation across all supported languages in the same pull request, rejecting partial translations.

What elements does the rule protect from translation?

It prohibits translating code, paths, URLs, environment variables, CLI flags, HTTP status codes, and Claude Code tool names such as Bash and Agent.

Source text

i18n-parity.md · MIT
---
paths:
  - "client/src/i18n/**"
  - "client/src/components/Sidebar.tsx"
  - "client/src/lib/format.ts"
  - "client/src/lib/paletteCommands.ts"
  - "README.md"
  - "README-EN.md"
  - "README-CN.md"
  - "README-VN.md"
  - "README-KO.md"
  - "README-ES.md"
  - "docs/I18N.md"
---

# i18n Parity Rules (binding for every coding agent)

The dashboard is localized to **English (`en`), Simplified Chinese (`zh`),
Vietnamese (`vi`), Korean (`ko`), and Spanish (`es`)** across five independent
surfaces. English is the source of truth on all of them, and **a change is not
done until every supported language carries it in the same PR** — a fallback to
English is a safety net, never a completed translation.

The full workflow, the surface map, the new-language checklist, and the
glossary live in [`.claude/skills/i18n-parity/`](../skills/i18n-parity/SKILL.md).
Invoke that skill for anything beyond a single-key edit. It is mirrored to
`.agents/skills/i18n-parity/` and `.codex/skills/i18n-parity/` so Codex and
other agents get the same instructions; **edit the canonical `.claude/` copy and
re-run `bash .claude/skills/i18n-parity/scripts/sync-agent-mirrors.sh`** — the
audit fails on a stale mirror.

## Non-negotiables

- **Adding an i18n key** → add it to `client/src/i18n/locales/en/<ns>.json` **and
  every other locale's `<ns>.json`**, with the same key path, the same value
  type, and the same `{{interpolation}}` tokens. Enforced by
  `client/src/i18n/__tests__/i18n.test.ts`.
- **Adding a namespace** → create the JSON for every locale, then register the
  imports, the per-language `resources` entry, and the `ns` array in
  `client/src/i18n/index.ts`.
- **Editing `README.md`** → keep the English-only landing concise and preserve
  links to `README-EN.md` plus every localized full guide.
- **Editing `README-EN.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. They are full mirrors, not summaries.
- **Editing user-visible text in `wiki/index.html`** → follow
  [`.claude/rules/wiki-i18n.md`](./wiki-i18n.md) and ship `zh` + `vi` + `ko` +
  `es` entries in the same change, then bump the wiki cache versions.
- **Adding a language** → work through
  [`.claude/skills/i18n-parity/references/new-language-checklist.md`](../skills/i18n-parity/references/new-language-checklist.md)
  end to end. A complete README mirror, every app key, and a complete wiki
  translation are all required; partial locales are not merged.
- **Never translate** code, commands, paths, URLs, env-var names, CLI flags,
  identifiers, HTTP verbs/status codes, numbers with units, brand names, hook
  event names (`PreToolUse`, `Stop`, …), or Claude Code tool names (`Bash`,
  `Agent`, `Read`, `Edit`). Translate only the prose around them.
- **The Claude Code tool `Agent` and the UI noun "agent" are different things.**
  The tool name is an identifier and stays literal in every locale. The UI noun
  (`common:agent` / `common:subagent`) is literal in `zh`, `vi`, and `ko` but
  deliberately `agente` / `subagente` in `es` — `i18n.test.ts` asserts both
  halves. The Spanish exception never applies to the tool name.
- The root landing page `index.html` and repository landing `README.md` are
  **English-only by design**. The complete localized guide set begins with
  `README-EN.md`.

## Verify

```bash
bash .claude/skills/i18n-parity/scripts/i18n-audit.sh   # must exit 0
npm run test:client
```

The audit reads `supportedLngs` from `client/src/i18n/index.ts`, so declaring a
locale there immediately turns every unfilled surface into a named failure.

© hoangsonww · MIT · hoangsonww/Claude-Code-Agent-Monitor

Similar IDE rules

All IDE rules for Frontend and UI →

From the same set155

The whole set →
error-propagation error-propagation finds the depth in a multi-agent tree where a failure started and tracks the chain that carried it up to parent agents. CX Codex +1 ★ 1,198repo stars issue-triager issue-triager diagnoses Claude Code Agent Monitor failures across the Express API, SQLite store, and hooks, returning concrete remediation steps. CX Codex ★ 1,198repo stars insights-advisor insights-advisor is a Claude Code subagent that examines Agent Monitor data and connects patterns across sessions. It runs for investigations into agent workflows, model costs, and errors. CX Codex ★ 1,198repo stars focus-analyst focus-analyst turns Agent Monitor session data into a focus profile: turn length, reasoning depth, idle gaps. Then it suggests 1–3 deep-work blocks for the week. CX Codex ★ 1,198repo stars trend-forecaster The trend-forecaster subagent projects Claude Code usage and spend from Agent Monitor history. Use it to check expected activity and cost over the coming weeks. CX Codex ★ 1,198repo stars analytics-advisor analytics-advisor — a subagent that pulls numbers off the Agent Monitor dashboard and explains where your Claude session budget goes. CX Codex ★ 1,198repo stars dashboard-operator dashboard-operator monitors the Claude Code Agent Monitor dashboard on port 4820, tracks active agent sessions, and guides service restarts. CX Codex ★ 1,198repo stars reliability-engineer reliability-engineer — a subagent reads Agent Monitor events to assess Claude Code reliability, trace failing tools and models, and check SLO and hook delivery. CX Codex ★ 1,198repo stars

Project sponsors

Companies that keep this analytics open