i18n-expert

Configure and audit internationalization for React, Next.js, and Vue projects.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/aleister1102/skills --skill i18n-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-expert
Source: https://github.com/aleister1102/skills/tree/main/i18n-expert
Command: npx skills add https://github.com/aleister1102/skills --skill i18n-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The i18n setup and auditing workflow helps teams replace hard-coded UI strings with localization keys, ensure consistent en-US/zh-CN parity, and validate pluralization and formatting across the app.

Core Features & Use Cases

  • Library selection and setup for React, Next.js, and Vue projects.
  • Locale file organization and translation workflow establishment, including structure and namespaces.
  • Audit, parity validation, and routing/language-detection configuration to support locale-aware UX.
  • RTL support checks and SEO/metadata localization considerations where applicable.

Quick Start

Initialize a baseline i18n setup for your frontend project and run the audit script to validate localization coverage.

Frequently Asked Questions about i18n-expert

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

FAQPage Schema
How do I set up internationalization in a React or Next.js project?

To set up internationalization in React or Next.js, you need to select an i18n library, configure locale file organization with namespaces, and establish language routing. This workflow replaces hard-coded UI strings with structured localization keys.

What is the best way to audit translation parity across frontend apps?

Auditing translation parity involves running automated checks to validate locale coverage and ensure consistent en-US/zh-CN translations. This process verifies pluralization, formatting, and routing configurations across the entire frontend codebase.

Does this i18n setup workflow support Vue applications?

Yes, the i18n setup and auditing workflow explicitly supports Vue applications. It handles library selection, locale file organization, and language routing to establish complete internationalization across Vue projects.

How do I replace hard-coded UI strings with translation keys?

Replacing hard-coded UI strings with translation keys requires mapping text elements to structured localization files. The workflow establishes namespaces and translation workflows to systematically substitute direct text with locale-aware keys.

Can I validate RTL support and SEO metadata during frontend localization?

Yes, the internationalization workflow includes RTL support checks and SEO metadata localization considerations. These checks ensure locale-aware user experience compliance and proper metadata configuration across supported languages.