What problem does it solve? Translation files drift out of sync as products evolve: some languages miss keys, others contain orphaned keys, and developers hardcode user-facing strings directly in the UI. This Skill audits internationalization parity so every locale stays consistent with the reference language. ## Core Features & Use Cases - Key Parity Comparison: Compares each locale against the reference language and reports missing keys, orphaned keys, and empty or untranslated values. - Hardcoded String Detection: Scans UI source code for user-facing strings that bypass the i18n system, listing each with file and line number. - Convention-Driven: Reads the project's docs/conventions/i18n.md to respect the actual locale file format, directory layout, and translation rules. - Use Case: Before a release, ask for an i18n audit to confirm Spanish and French locales contain every key present in the English reference and that no hardcoded labels slipped into new components. ## Quick Start Ask the assistant to review the project's translations and check whether all languages are synchronized with the reference locale.