What problem does it solve? Hardcoded user-facing text scattered across components makes applications impossible to translate and localize. This Skill audits codebases for untranslated strings, checks that locale files share consistent keys across languages, and enforces proper formatting of dates, currencies, and numbers for the es-CO locale in a Next.js App Router project. ## Core Features & Use Cases - Hardcoded String Detection: Scans JSX, Vue, and Python files for text literals in elements, placeholders, labels, and error messages that bypass translation catalogs. - Locale Completeness Check: Compares JSON translation files across languages and reports missing or extra keys per namespace. - Localization Guidelines: Provides rules for message catalog organization, Intl API-based formatting of COP currency, dates in America/Bogota timezone, and pluralization. - Use Case: Before releasing a new feature, run the checker against your frontend to find untranslated button labels and verify that the es-CO message catalog has no missing keys. ## Quick Start Run the i18n checker script against my project directory and report any hardcoded strings or missing translation keys.
