Skip to content

i18n Expert

i18n

Full internationalization setup and audit pipeline for React, Next.js, and Vue applications.

Overview

This skill delivers a complete i18n workflow: configure the i18n framework, replace hard-coded user-facing strings with translation keys, ensure locale parity across languages, and validate pluralization and formatting. It defaults to en-US and zh-CN coverage and follows a strict Audit, Fix, Validate cycle to eliminate missing translations.

When to Use

  • Setting up i18n from scratch in a React, Next.js, or Vue project
  • Auditing an existing codebase for untranslated strings
  • Ensuring key parity between locale files (e.g., en-US and zh-CN)
  • Replacing raw user-facing text with t('key') calls
  • Localizing error messages, accessibility labels, and metadata

Key Features

  • Framework-aware library selection: react-i18next for React, next-intl for Next.js, vue-i18n for Vue
  • Structured workflow: Audit (scan for raw strings and missing keys) then Fix (replace and add keys) then Validate (re-audit until zero issues)
  • Bundled audit script: scripts/i18n_audit.py extracts t('key') usage and compares against locale JSON files
  • Namespace architecture: Encourages nested key structures (errors.*, buttons.*, workspace.*) for maintainability
  • Guardrails: Never exposes raw error.message to UI; preserves placeholders and plural rules; respects brand terms

Example Prompts

text
Set up i18n for my Next.js app with en-US and zh-CN support using next-intl.

Audit my React project for untranslated strings and fix locale parity gaps.

Add Chinese translations for all error messages in my Vue application.

Source

Managed with Obsidian · Rendered by VitePress