localization-toolkit

# 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) 1) Confirm scope and locale targets - Identify the i18n framework and locale locations. - Confirm locales; default to en-US + zh-CN when specified. 2) Setup i18n baseline (if missing) - Choose a framework-appropriate library (e.g., React: react-i18next; Next.js: next-intl; Vue: vue-i18n). - Install packages and create the i18n entry/config file. - Wire the provider at the app root and load locale resources. - Add a language switcher and persistence (route/param/localStorage) as appropriate. - Establish locale file layout and key namespaces. - If routing is locale-aware, define...