manage-translations

Update and create JSON translation files for IGOOR plugins and app locales.

8|1|Updated Feb 24, 2025
One-click install
npx skills add https://github.com/igoor-noprofit/igoor --skill manage-translations-igoor-noprofit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-translations
Source: https://github.com/igoor-noprofit/igoor/tree/main/.factory/skills/manage-translations
Command: npx skills add https://github.com/igoor-noprofit/igoor --skill manage-translations-igoor-noprofit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping IGOOR's multilingual interface consistent is tedious: when French source strings change, every other language file can silently fall out of sync, and adding a new language requires recreating the full key structure across plugin and app locale directories. ## Core Features & Use Cases - Synchronize existing languages: Compare target language JSON files against the French source of truth and fill in missing keys without overwriting valid existing translations. - Add new languages: Create the full locale directory structure and translation files for a new language code (e.g., de_DE, es_ES) following the {language}_{REGION} convention. - Handle special structures: Correctly process nested files like biorecorder questions JSON and language-parameterized AI prompts in prompts.yaml. - Use Case: After updating French strings in the onboarding plugin, run this Skill to propagate the new keys into every other supported language file with proper translations. ## Quick Start Update the German translations for the onboarding plugin to match the current French source file.

Frequently Asked Questions about manage-translations

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

FAQPage Schema
How do I add a new language to the IGOOR app?

Create a locale directory using the {language}_{REGION} format (e.g., de_DE) inside each plugin's locales folder, copy the French source JSON structure, and translate all values. Also add entries to LANG_TO_NAME and LANG_STYLE_NOTES in settings_manager.py for AI prompt language support.

How do I sync missing translation keys across languages?

Compare the target language JSON file against the French source file, which is the source of truth. Add any missing keys with translated values while preserving existing translations, and verify both files have identical key sets.

Does IGOOR need English translation files?

No, English (en_EN) is the default language and needs no translation files. The application uses English strings directly, and when a translation file is missing it falls back to displaying the original English strings.

Why are my translations showing in English instead of the selected language?

This usually means the translation file is missing, in the wrong location, or the language code does not match exactly (codes are case-sensitive). Verify the file path follows plugins/{plugin}/locales/{lang}/{plugin}_{lang}.json and restart the application.

What causes JSON parsing errors in translation files?

Common causes are trailing commas, improperly quoted strings, and unescaped special characters. Validate that each file is well-formed UTF-8 JSON with unique keys before testing in the application.

Do I need to translate prompts.yaml for each language?

No, AI prompts live in a single prompts.yaml per plugin and are language-parameterized via {reply_language} placeholders filled at runtime. Never duplicate prompts.yaml per locale; only update the language mapping dictionaries in settings_manager.py.