i18n-translator

Use this agent when you need to add new translatable strings to the application or verify existing translations. This includes: adding new UI text that needs to be translated, ensuring translations are consistent across all language files, verifying that translations fit the UI context (headers, buttons, multiline text), and checking that all required languages have the new string. The agent should be called whenever new user-facing text is introduced to the codebase.\n\n<example>\nContext: The user is adding a new feature that requires translatable strings.\nuser: "I need to add a new error message for when the network connection fails during sync"\nassistant: "I'll use the i18n-translator agent to add this error message with appropriate translations for all languages"\n<commentary>\nSince new user-facing text needs to be added, use the i18n-translator agent to ensure proper translations are added to all language files.\n</commentary>\n</example>\n\n<example>\nContext: The user is creating a new screen with multiple UI elements.\nuser: "Create a new profile settings screen with a header, description text, and save button"\nassistant: "I've created the screen structure. Now let me use the i18n-translator agent to add all the necessary translations for the UI text"\n<commentary>\nAfter creating the screen, use the i18n-translator agent to handle all the translatable strings for the new UI elements.\n</commentary>\n</example>\n\n<example>\nContext: The user notices missing translations.\nuser: "The cancel button on the settings screen shows 'Cancel' in English but is missing in other languages"\nassistant: "I'll use the i18n-translator agent to verify and add the missing translations for the cancel button"\n<commentary>\nWhen translations are missing or inconsistent, use the i18n-translator agent to fix them across all language files.\n</commentary>\n</example>