i18n

Automate i18n key enforcement and locale validation across multilingual projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Internationalization (i18n) introduces translation management overhead, risk of hard-coded strings, and inconsistent terminology across software. This skill provides a centralized workflow and standards to ensure translations are applied consistently across languages and modules.

Core Features & Use Cases

  • Enforces usage of i18n keys for all user-visible text to ensure consistency.
  • Centralizes language and module configuration via i18n-config.json and the locales directory.
  • Guides adding new translations and modules, validating cross-language coverage across locales.

Quick Start

Update the i18n-config.json to add the new language and run the i18n workflow to propagate translations.

Frequently Asked Questions about i18n

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

FAQPage Schema
How do I manage app translations and prevent hard-coded strings in my project?▼

App translations are managed by enforcing i18n keys for all user-visible strings, eliminating hard-coded text. This workflow ensures consistent terminology across web and desktop projects by centralizing language configuration and validating locale updates.

What is the best way to add a new language to an existing internationalization workflow?▼

To add a new language to an internationalization workflow, update the i18n-config.json file with the new locale and execute the translation workflow. This automatically propagates and validates translations across all project modules.

How do I validate cross-language coverage for multilingual user interfaces?▼

Cross-language coverage is validated by coordinating locale updates with built-in validation checks. The workflow reads languages and modules from i18n-config.json to ensure all translations are consistently applied across the locales directory.

Does this internationalization workflow work for both web and desktop projects?▼

This internationalization workflow explicitly supports both web and desktop projects requiring multilingual user interfaces. It applies standardized terminology and localization rules universally across different application platforms.

What configuration do I need to set up before starting app localization?▼

App localization requires a central i18n-config.json file and a designated locales directory to define languages and modules. This configuration acts as the single source of truth for the workflow to read and apply translation updates.

Why do I need standardized terminology for software internationalization?▼

Standardized terminology is needed because internationalization introduces translation management overhead and risks inconsistent wording across languages. Enforcing i18n keys provides a centralized workflow to ensure all user-visible strings remain consistent globally.