Enforce i18n translation keys in Blaze templates and JavaScript.
npx skills add https://github.com/zcawood-mie/agentz --skill i18n-text
Please help me install this Agent Skill. Skill: i18n-text Source: https://github.com/zcawood-mie/agentz/tree/main/skills/i18n-text Command: npx skills add https://github.com/zcawood-mie/agentz --skill i18n-text
Prevents hardcoded user-facing strings by enforcing use of i18n translation keys and a consistent translation workflow, reducing localization regressions and inconsistent messaging across the UI. It guides developers to avoid embedding literal text in templates and JavaScript and ensures parity across multiple language files.
Ask the agent to add a new i18n key save_changes with English value Save Changes and update all nine language files so keys remain alphabetized and valid.
High-intent search queries and answers about installing and using this skill.
To enforce i18n and prevent hardcoded UI strings, all user-facing text such as labels, buttons, and alerts must use translation keys instead of literal text in Blaze templates and JavaScript. This ensures consistent messaging and reduces localization regressions across the UI.
You can atomically add a new i18n translation key across all nine language JSON files using provided helper scripts. These scripts validate snake_case naming, insert the key while preserving alphabetical sort order, and support dry-run and force options for safe multi-language updates.
Translation keys must use descriptive snake_case naming conventions. For dynamic content, interpolation must use the {$variable} syntax to ensure safe substitutions and consistent variable formatting across all localized user-facing strings in the application.
Yes, this i18n enforcement workflow specifically supports Blaze templates and JavaScript in projects using the universe:i18n bluehive-i18n package. It validates translation keys and maintains alphabetically sorted JSON files across nine languages within this specific stack.
Inconsistent localization JSON files occur when new translation keys are not added atomically across all nine language files. Using a validation script that enforces alphabetical sorting and snake_case naming ensures parity and prevents missing keys across different languages.
The best way to manage multi-language translation workflows is to enforce a consistent process using translation keys for all user-facing strings and helper scripts. This approach validates key naming, ensures alphabetical sorting across nine language files, and maintains UI parity.
buihuulocScan Unreal Engine C++ and Blueprint codebases for hardcoded strings and localization issues.
jellyrockAdd compliant translation keys to JellyRock's JSON i18n system.
NabilThangeDetect hardcoded strings and manage translations for software localization.
arbazkhan971Audit and implement internationalization across React, Vue, or Angular codebases.
