i18n-expert
i18n-expert guides you through complete internationalization setup and auditing for React, Next.js, and Vue codebases. It handles framework selection, locale file organization, string replacement with translation keys, and validation of locale parity across your target languages. The skill ensures proper error localization, metadata translation, and language switching with persistence.
i18n-expert sets up and configures internationalization frameworks for React, Next.js, and Vue with locale file management.
AI-generated summary based on this skill's SKILL.md
Install
daymade/claude-code-skills/i18n-expert · repository language: Python
git clone https://github.com/daymade/claude-code-skills
cp -r claude-code-skills/i18n-expert ~/.claude/skills/i18n-expertFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I set up i18n in React?
i18n-expert walks you through React internationalization setup by helping you choose a framework (react-i18next, react-intl, or similar), organize locale files by language and namespace, configure the i18n instance with fallback locales, and integrate it into your component tree. The skill guides you through initializing translation resources, setting default language, and exposing the i18n hook or context to your components so you can access translations throughout your app.
What does i18n-expert do for locale file parity?
i18n-expert audits and fixes missing translation keys and locale parity issues by scanning your locale files across all target languages (en-US, zh-CN, etc.) to identify keys present in one language but absent in others. It flags incomplete translations, suggests key additions, and helps you validate that every language file has matching structure and coverage, ensuring consistent user experience across all supported locales.
How do I replace hardcoded strings with translation keys?
i18n-expert helps you systematically replace hardcoded UI strings with localized translation keys by identifying all hard-coded text in your codebase, extracting it into your locale files, and refactoring components to use i18n translation functions (like `t('key')` in react-i18next). The skill provides strategies for organizing keys by feature or page, managing pluralization, and handling dynamic content within translations.
Can i18n-expert help with Next.js internationalization routing?
Yes. i18n-expert guides you through Next.js internationalization routing by setting up locale-prefixed routes (e.g., `/en/page`, `/zh/page`), configuring middleware to detect and persist user language preference, implementing language switchers that preserve route structure, and ensuring SEO metadata (title, description) is localized per language. It covers both file-based and dynamic routing approaches for Next.js 12+.
How do I localize error messages and date/number formatting?
i18n-expert handles localization of error messages, pluralization, and date/number formatting by showing you how to store error strings in locale files with context-aware keys, use i18n pluralization rules for quantity-dependent text, and integrate locale-aware formatters (Intl API or date-fns) for dates, times, and numbers. The skill ensures formatting respects regional conventions (e.g., DD/MM/YYYY vs MM/DD/YYYY) and RTL language requirements.
What's the best way to implement language switching with persistence?
i18n-expert recommends storing user language preference in localStorage or a database, creating a language switcher component that updates the i18n instance and persists the choice, and using middleware (in Next.js) or route guards (in Vue) to apply the saved locale on app load. The skill covers cookie-based and URL-based persistence strategies, ensuring language preference survives page reloads and works across your entire application.
SKILL.md
rendered from the published skill — quoted content, verbatim
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
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 3 files
i18n-expert/.security-scan-passed
i18n-expert/SKILL.md
i18n-expert/scripts/i18n_audit.py