i18n-expert

1# I18n Expert
2 
3## Overview
4 
5Deliver 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.
6 
7## Core Capabilities
8 
9- Library selection and setup (React, Next.js, Vue).
10- Key architecture and locale file organization.
11- Translation generation and quality strategy (AI, professional, manual).
12- Routing and language detection/switching.
13- SEO and metadata localization (when applicable).
14- RTL support (only if RTL locales are in scope).
15 
16## Scope Inputs (ask if unclear)
17 
18- Framework and routing style.
19- Existing i18n state (none, partial, legacy).
20- Target locales (default: en-US + zh-CN).
21- Translation quality needs (AI vs professional vs manual).
22- Locale formats in use (JSON, YAML, PO, XLIFF).
23- Formality/cultural requirements (if any).
24 
25## Workflow (Audit -> Fix -> Validate)
26 
271) Confirm scope and locale targets
28- Identify the i18n framework and locale locations.
29- Confirm locales; default to en-US + zh-CN when specified.
30 
312) Setup i18n baseline (if missing)
32- Choose a framework-appropriate library (e.g., React: react-i18next; Next.js: next-intl; Vue: vue-i18n).
33- Install packages and create the i18n entry/config file.
34- Wire the provider at the app root and load locale resources.
35- Add a language switcher and persistence (route/param/localStorage) as appropriate.
36- Establish locale file layout and key namespaces.
37…