i18n-text

What problem does it solve?

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.

Core Features & Use Cases

• Enforcement Guidance: Rules that require all labels, buttons, placeholders, headings, alerts, toasts, error messages, tooltips, and modal content to use translation keys instead of hardcoded text.
• Naming & Interpolation Conventions: Snake_case keys, descriptive names, and interpolation using {$variable} to ensure consistent, safe substitutions.
• Multi-language Workflow: Instructions and helper scripts to verify presence across nine language JSON files and to add keys atomically while preserving alphabetical sort.
• Developer Tools: Scripts to search for existing keys and to add new keys across all language files, with validation, dry-run, and force options.

Quick Start

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.