What problem does it solve? Hardcoded user-facing text scattered across backend messages, frontend pages, and validation annotations makes multi-language support error-prone and hard to audit. This Skill orchestrates a controlled transformation that replaces hardcoded copy with resource-file keys while guaranteeing zero business-logic changes. ## Core Features & Use Cases - Three transformation tracks: backend messages (error codes, exceptions, prompts), frontend copy (labels, buttons, placeholders, dialogs, breadcrumbs, options), and parameter validation annotation messages. - Orchestrated subagent pipeline: one file equals one transformation subagent, followed by independent read-only review subagents (fatal/warning grading) and validation subagents (key-set consistency, encoding, mapping completeness), with at most 2 repair rounds before escalating to a manual-intervention list. - Key conventions and reporting: enforces naming structure, prefix ownership, multi-language key-set parity, escaped non-Latin values, append-only resource edits with backups, and produces transformation reports plus new-key glossaries. - Use Case: Ask to internationalize a module; the Skill scans for hardcoded strings, confirms scope with you, dispatches per-file transformation agents, then reviews, validates, compiles, and commits the changes. ## Quick Start Use the i18n-transform skill to convert all hardcoded Chinese copy in the order-management module into resource file keys with English translations.
