What problem does it solve?
Localization teams often work blind, manually searching for hardcoded UI strings and balancing translators without a consistent workflow. Without enforcement, missing keys, placeholder mismatches, and stale translations slip into builds, causing broken experiences across languages.
Core Features & Use Cases
- Scan anti-patterns: Search src/ for literal text, concatenations, and locale-unaware formatting while flagging embedded text in assets and assumptions that ignore right-to-left languages.
- Extract keys and diff: Compare source strings against assets/data tables, propose descriptive keys following category conventions, and output diffs for reviewer approval.
- Validate coverage and issues: Verify translator comments, placeholder consistency, character limits, missing translations, and orphaned entries while grouping results by locale.
Use Case: After a UI sprint adds new copy, run the extract and validate commands to refresh the string tables and produce a coverage matrix before handing work to translators.
Quick Start
Ask the localization skill to run the scan command on src to list hardcoded strings and localization anti-patterns.