localization

Routes i18n and l10n tasks to translation sync, review, extraction, and linting sub-skills.

3|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill localization-jose-polanco-oxte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localization
Source: https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer/tree/main/.agents/skills/localization
Command: npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill localization-jose-polanco-oxte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing translations across multiple languages is error-prone: keys go missing, placeholders get dropped, terminology drifts, and hardcoded strings slip into source code. This Skill acts as a router that directs any internationalization or localization task to the right specialized workflow, so translation files stay complete, consistent, and safe to ship. ## Core Features & Use Cases - Task Routing: Reads the task at hand and loads only the matching sub-skill, covering translation sync, adding languages, string extraction, format conversion, style guides, health audits, quality review, and locale linting. - Translation Sync & Linting: Synchronizes locale files by translating only changed keys while preserving variables and glossary terms, and validates files with the translint checker for missing keys, placeholder mismatches, and untranslated values across JSON, PO, and Properties formats. - Use Case: After adding a new key to your base en.json locale file, use this Skill to route to translation-sync so French, German, and Japanese files receive only the new translation, then run translint to confirm no placeholder mismatches before opening the pull request. ## Quick Start Ask the assistant to sync the project's translation files after adding new keys to the English locale, and it will load the matching localization sub-skill to translate the delta and validate the results.

Frequently Asked Questions about localization

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

FAQPage Schema
How do I sync translation files across multiple languages?

Use the translation-sync sub-skill, which reads your source locale file, detects changed keys via git diff, and translates only the delta into each target language. It preserves variables, enforces glossary terms, and writes files atomically so existing translations are never corrupted.

How to check locale files for missing keys and placeholder mismatches?

Run the translint sub-skill against your locale directory with a base language flag. It reports missing keys, extra keys, placeholder mismatches, empty values, and untranslated strings for JSON, gettext PO, and Java Properties files, exiting nonzero when issues exist.

What i18n file formats and frameworks are supported?

The sub-skills handle JSON, YAML, PO/Gettext, XLIFF, ARB, and Java Properties formats. Framework detection covers react-intl, i18next, vue-i18n, Angular localize, svelte-i18n, Flutter intl, Rails i18n, Django, and Laravel for string extraction.

Can I convert translation files between JSON, PO, and XLIFF formats?

Yes, the translation-convert sub-skill converts between JSON, YAML, PO, XLIFF, ARB, and Properties while preserving keys, variables, pluralization rules, and metadata. Original files stay intact and output is validated by re-parsing and comparing key counts.

Why does a placeholder mismatch in translations cause runtime errors?

When a translated string drops or renames an interpolation token like {name} or %s, the formatting call throws a KeyError or IndexError the first time that string renders with real data. Translint catches these mismatches by comparing token sets between base and translated values.

When should I not rely on automated translation sync?

Avoid fully automated sync when legal, medical, or brand-critical copy requires certified human review, or when the untranslated-value heuristic flags legitimate cognates and brand names. Use the review sub-skill and glossary do-not-translate lists to keep those cases under manual control.