What problem does it solve? Applications built with hardcoded text cannot be translated, and retrofitting internationalization by hand is error-prone: plurals get hand-branched, strings get concatenated, and RTL layouts break. This Skill systematically externalizes every user-facing string into the i18n mechanism the project already uses, so the app becomes translation-ready without adopting a new framework. ## Core Features & Use Cases - String extraction and refactoring: Scans source for hardcoded user-facing text, assigns semantic screen.component.element.purpose keys, and replaces literals with lookups through the platform's native i18n mechanism. - Locale resource generation: Produces base-locale resource files split by feature, with translator comments covering context, length limits, and variables, plus skeleton files for other locales. - Correctness rules for plurals, formatting, and RTL: Routes plurals through the platform's plural engine, formats dates and currency with locale-aware formatters, and uses logical start/end direction for RTL support. - Use Case: A team preparing their web app for a German and Arabic launch invokes this role to externalize all UI copy, generate the English resource files, and verify layouts survive 40% text expansion before handing off to QA. ## Quick Start Ask the agent to act as the i18n-engineer and externalize all hardcoded user-facing strings in the current project into its existing i18n framework, generating the base locale resource files.
