i18nlisted

# Internationalization (i18n) ## When to use Use this skill when adding a new language, introducing a framework's i18n library, or centralizing hard-coded copy. ## Steps 1. Find user-facing strings: JSX text, template literals, alert/button labels. 2. Replace them with translation calls (e.g. `t('key')`) using stable, namespaced keys. 3. Generate or update locale JSON files, keeping keys consistent across languages. 4. Handle plurals, interpolation, and date/number formatting via the library. 5. Verify no string is left hard-coded and that the fallback locale renders. ## Examples - "Make this React app translatable" - "Extract strings into locale/en.json" ## References Keys should be semantic ("settings.title"), not the English text; never concatenate translated fragments in a way that breaks word order.