i18n

Plan and implement a scalable internationalization workflow with centralized i18n-config.json and locale JSON files.

7|2|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/bitan-del/gods-eye-desktop --skill i18n-bitan-del
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n
Source: https://github.com/bitan-del/gods-eye-desktop/tree/main/.claude/skills/i18n
Command: npx skills add https://github.com/bitan-del/gods-eye-desktop --skill i18n-bitan-del

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Internationalization (i18n) workflow and standards for managing translations. This skill provides a structured approach to ensure consistent translation workflows across the app, from text extraction to module-level coverage and validation.

Core Features & Use Cases

  • Establishes a centralized i18n configuration and reference language, ensuring all UI text is translated and consistent.
  • Guides adding new translation modules, updating locale files, and validating coverage across languages.
  • Use Case: A development team adds a new feature with user-visible text and runs this skill to propagate translations across all locales and modules.

Quick Start

Run the i18n workflow to load the current languages and modules, then apply translations to new user-facing text.

Frequently Asked Questions about i18n

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

FAQPage Schema
How do I set up a scalable internationalization workflow for user-facing text?

To set up a scalable internationalization workflow, you need a centralized i18n-config.json file and locale JSON files per module. This structure establishes a reference language and applies automated validation to ensure consistent translation coverage.

What is the best way to maintain translation consistency across multiple locales?

Translation consistency across multiple locales is maintained through automated validation checks against a reference language. By organizing locale JSON files per module and enforcing a centralized configuration, the workflow ensures comprehensive localization without missing text.

How do I add new translation modules and propagate updates across all locale files?

Adding new translation modules involves running the i18n workflow to load current languages, then applying new user-facing text to update locale files. This propagates translations across all configured languages and validates module-level coverage automatically.

Do I need a centralized configuration file to manage app localization?

Yes, a centralized i18n-config.json file is required to manage app localization effectively. It establishes the reference language, guides module updates, and runs automated validation to ensure comprehensive text translation across all locales.

When do I need automated validation for my i18n workflow?

Automated validation for your i18n workflow is needed when adding new features with user-visible text across multiple modules. It ensures comprehensive localization by checking translation coverage and consistency across all configured languages and locale files.