i18n-completeness

Missing translation keys are identified by analyzing code usage against JSON translation files. This Skill detects keys used in code but absent from locale files, flagging runtime gaps across English, Japanese, and Chinese Simplified translations so you can add them before deployment.

Hardcoded strings violate i18n compliance when they bypass the t() translation function. This Skill scans for non-translated text in code and templates, distinguishing strings that must use t() from those already localized, so you achieve consistent key deployment.

Dynamic key patterns are validated by analyzing template literal usage and key generation logic. This Skill detects patterns such as t(`game.${type}`) and confirms the required keys exist in all locale files, preventing runtime translation failures.

Running the check analyzes your entire codebase for missing keys, hardcoded strings, dynamic patterns, and unused keys across all locale files. It enforces i18n compliance by validating JSON integrity and coordinating fixes across English, Japanese, and Chinese Simplified translations.

Unused keys are found by comparing all keys in translation files against actual code usage. This Skill flags keys not referenced anywhere, enabling cleanup of obsolete translations and keeping locale files lean and maintainable.