This skill should be used when setting up, auditing, or enforcing internationalization/localization in UI codebases (React/TS, i18next or similar, JSON locales), including installing/configuring the i18n framework, replacing hard-coded strings, ensuring en-US/zh-CN coverage, mapping error codes to localized messages, and validating key parity, pluralization, and formatting.
SkillScore86Maintained
Automatic
◆Translation & Localization pack
Last verified 8/10/2026
What it changes
Passed 19 of 22 test cases with the skill, and 17 of 22 without it.
Without skill77%
With skill86%
Checks it passed that the model alone missed
Configures en-US as a target locale.
Configures zh-CN as a target locale.
Sets zh-CN as a default target locale.
2 fixed17 passed either way3 still failing0 broke
Pass-rate lift
+9 pp
Tokens
+30%
Agent turns
0%
Response time
-18%
Model gemini-3.6-flashMeasured 8/10/2026v119 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
We are setting up localization for a newly created repository. The product manager asked us to set up locale files but didn't specify which target languages to start with. Which target locales should be configured by default?
What was checked, without and with the skill
Checked
Without skill
With skill
Sets en-US as a default target locale.
Passed
Passed
Sets zh-CN as a default target locale.
Missed
Passed
case-18 · gemini-3.6-flash · 8/10/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md123 lines2 filesincludes scripts
I18n Expert
Overview
Deliver a complete i18n setup + audit pass: configure the i18n framework, replace user-facing strings with keys, ensure locale parity, and validate pluralization/formatting for en-US and zh-CN.
Core Capabilities
Library selection and setup (React, Next.js, Vue).
Key architecture and locale file organization.
Translation generation and quality strategy (AI, professional, manual).
Routing and language detection/switching.
SEO and metadata localization (when applicable).
RTL support (only if RTL locales are in scope).
Scope Inputs (ask if unclear)
Framework and routing style.
Existing i18n state (none, partial, legacy).
Target locales (default: en-US + zh-CN).
Translation quality needs (AI vs professional vs manual).
Locale formats in use (JSON, YAML, PO, XLIFF).
Formality/cultural requirements (if any).
Workflow (Audit -> Fix -> Validate)
Confirm scope and locale targets
Identify the i18n framework and locale locations.
Confirm locales; default to en-US + zh-CN when specified.