Enforce i18n key synchronization and language sync rules for SpotiArr frontend.
npx skills add https://github.com/mralexsaavedra/spotiarr --skill spotiarr-i18n
Please help me install this Agent Skill. Skill: spotiarr-i18n Source: https://github.com/mralexsaavedra/spotiarr/tree/main/skills/spotiarr-i18n Command: npx skills add https://github.com/mralexsaavedra/spotiarr --skill spotiarr-i18n
This skill prevents missing or inconsistent localization keys in the SpotiArr frontend by enforcing how languages, i18n resources, and key conventions are maintained.
UI_LANGUAGE backend configuration using useLanguageSync rather than ad-hoc browser detection or manual language switching.escapeValue: false expectations so translation strings can include HTML without accidental escaping, while warning against untrusted content.Update SpotiArr’s frontend by adding your new translation keys in both en.json and es.json, then follow the key conventions used in src/locales while relying on UI_LANGUAGE for language switching.
High-intent search queries and answers about installing and using this skill.
To keep i18n translation keys consistent, you must synchronize new keys across all locale files like en.json and es.json using standardized dot-notation paths. This prevents silent fallbacks and missing string errors during frontend localization.
Your HTML tags are disappearing because the i18next configuration uses escapeValue: false. This policy allows translation strings to include HTML without accidental escaping, though you should avoid using untrusted content to prevent security issues.
You sync the UI language by using the useLanguageSync hook to follow the UI_LANGUAGE backend configuration. This enforces reliable language synchronization instead of relying on ad-hoc browser detection or manual language switching.
If you add a new i18n key to only one locale file, the application will experience silent fallbacks or missing translations. You must enforce synchronized key updates across all locale files to maintain correct internationalization behavior.
You should follow standardized dot-notation key paths and specified interpolation conventions when adding i18next translations. Maintaining this translation-key discipline ensures structured localization and prevents silent fallbacks across locale resources.
vechainManage react-i18next translation JSON files across multiple languages.
andershi666Automate React translation management with flat dot-notation keys and locale exports.
weiloon1234Define reusable frontend forms with centralized state, validation, and 422 error handling.
mateo19182Automate React i18n tasks by extracting hardcoded strings and replacing them with translation keys.