i18n-localization

i18n & Localization Agent Skills

Skill Overview

Helps developers implement internationalization (i18n) and localization (l10n) for projects: automatically detects hard-coded strings, manages translation files, and supports RTL (right-to-left) layouts.

Use Cases

Web Applications for Global Users

When your product needs to serve users across multiple countries/regions, this skill helps you implement multilingual support systematically—from React/Next.js frontends to Python backends.

Projects with Many Hard-Coded Strings

As the project grows, many text strings are accumulated directly inside components. This skill can quickly find these hard-coded strings using built-in detection scripts and provide remediation suggestions.

Support for RTL Languages (e.g., Arabic, Hebrew)

When entering Middle East markets, the UI layout needs to be fully mirrored. This skill offers best practices for CSS Logical Properties and RTL layout to ensure the interface displays correctly in RTL mode.

Core Features

Hard-Coded String Detection

Uses the i18n_checker.py script to scan your project code, automatically identifies hard-coded text not tied to translation keys, and generates a repair report. Supports detection for multiple languages and file types, including React and Python.

Translation File Structure Management

Provides a standard locale file organization approach, splitting translation content by functional module namespaces (e.g., common.json, auth.json) to prevent any single file from becoming too large. Supports handling plural forms for multiple languages.

RTL Layout Support Plan

Delivers a complete RTL adaptation guide, including how to use CSS Logical Properties, icon mirroring, switching text direction, and more—ensuring a great user experience for RTL languages like Arabic and Hebrew.

Frequently Asked Questions

What’s the difference between i18n and L10n?

i18n (Internationalization) is internationalization—it means making the app capable of being translated. L10n (Localization) is localization—the actual translation work. In short: i18n is preparation, and L10n is execution.

Which frameworks does this skill support?

This skill covers popular stacks such as React (react-i18next), Next.js (next-intl), and Python (gettext). It also provides general i18n best practices applicable to any programming language.

What happens if a translation is missing?

It’s recommended to configure a fallback language (usually English). If a translation is missing in the current language, the system automatically falls back to the default language to avoid blank output or displaying translation key names.