i18n-expert

Name: i18n-expert
Availability: InStock
Author: huubar

Audits and implements i18n in React/TS projects with JSON locale files.

Updated Apr 21, 2026

Search Tags:#react #localization #translation #i18n #internationalization #i18next #locales

Ready to run

npx skills add https://github.com/HuuBar/skill-routing-experiment --skill i18n-expert-huubar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: i18n-expert
Source: https://github.com/HuuBar/skill-routing-experiment/tree/main/unified_skills/daymade/i18n-expert
Command: npx skills add https://github.com/HuuBar/skill-routing-experiment --skill i18n-expert-huubar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Internationalization (i18n) in UI codebases is often manual, error-prone, and hard to scale across locales; this skill provides a repeatable setup and audit workflow to ensure consistent translations and locale parity across React/TS projects using JSON locales.

Core Features & Use Cases

Establish a robust i18n baseline (framework selection, config, locale file layout, and provider wiring).
Audit and enforce translation key parity, pluralization rules, and error-message mappings across en-US/zh-CN.
Use cases include adding new locales, validating coverage, and refactoring strings to keys while preserving placeholders.

Quick Start

Configure a baseline i18n setup and scaffold en-US/zh-CN locales for a React app, then run an audit to validate key parity.

Frequently Asked Questions about i18n-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I audit translation key parity between en-US and zh-CN locale files in React?▼

Audit translation key parity by comparing en-US and zh-CN JSON locale files to identify missing keys, orphaned entries, and mismatched pluralization rules across the React project.

What is the best way to set up i18next internationalization in a TypeScript UI app?▼

Set up i18next by configuring the framework, defining JSON locale file layouts, and wiring the provider to establish a robust internationalization baseline for the TypeScript UI app.

Can I use this i18n audit workflow to enforce pluralization rules and error-message mappings?▼

Yes, the i18n audit workflow enforces pluralization rules and validates error-to-message mappings, ensuring robust translation coverage across en-US and zh-CN locales.

How do I refactor UI strings to translation keys while preserving placeholders?▼

Refactor UI strings by mapping hardcoded text to JSON locale keys while preserving dynamic placeholders, ensuring locale parity and robust translations across the React project.

Does this internationalization setup support adding new locales beyond en-US and zh-CN?▼

Yes, the internationalization setup supports adding new locales by applying the established JSON locale file layout and running validation checks to ensure translation key parity.

When do I need to validate i18n locale coverage in a React project?▼

Validate i18n locale coverage when adding new locales, refactoring strings to keys, or auditing to ensure translation key parity and robust translations across the React codebase.