i18n

Implement react-i18next translations with flat dot notation keys.

Updated May 11, 2026
One-click install
npx skills add https://github.com/zmh13928433602-sys/lobe-chat --skill i18n-zmh13928433602-sys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n
Source: https://github.com/zmh13928433602-sys/lobe-chat/tree/main/.agents/skills/i18n
Command: npx skills add https://github.com/zmh13928433602-sys/lobe-chat --skill i18n-zmh13928433602-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Internationalization is essential to support multiple languages in React apps; this guide provides a structured approach to adding translations, managing locale data, and implementing react-i18next for consistent UI text.

Core Features & Use Cases

  • Standardizes translation keys with a flat dot notation for predictable lookups.
  • Guides on setting a default language, adding new locales, and generating translations.
  • Demonstrates how to integrate react-i18next into UI components and ensure scalable localization workflows.

Quick Start

Run pnpm i18n to generate translations for the default and additional locales.

Frequently Asked Questions about i18n

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

FAQPage Schema
How do I manage translations in a React application using react-i18next?

To manage translations in a React application, this Skill guides you through integrating react-i18next, setting a default language, adding locales, and running pnpm i18n to generate structured multilingual UI text.

What is the best way to name translation keys for scalable localization?

The best way to name translation keys for scalable localization is using a flat dot notation convention, which ensures predictable lookups and consistent multilingual text management across your React components.

How do I generate translation files for multiple locales in a React workflow?

You generate translation files for multiple locales by defining a default language and a key naming scheme, then executing the pnpm i18n command to automatically generate the required locale data.

Does this react-i18next workflow require a specific package manager to run?

Yes, this react-i18next workflow requires the pnpm package manager to execute the pnpm i18n command, which handles generating translations for the default and additional locales.

When do I need to configure a default language for my React app's internationalization?

You need to configure a default language for React internationalization before generating translations, as it serves as the foundational locale required to meet workflow constraints and ensure consistent UI text.