localize

When this skill is invoked:

1. Parse the subcommand from the argument:
2. scan — Scan for localization issues (hardcoded strings, missing keys)
3. extract — Extract new strings and generate/update string tables
4. validate — Validate existing translations for completeness and format
5. status — Report overall localization status

1. For scan:
2. Search src/ for hardcoded user-facing strings:
3. String literals in UI code that are not wrapped in a localization function
4. Concatenated strings that should be parameterized
5. Strings with positional placeholders (%s, %d) instead of named ones ({playerName})
6. Search for localization anti-patterns:
7. Date/time formatting not using locale-aware functions
8. Number formatting without locale awareness
9. Text embedded in images or textures (flag asset files)
10. Strings that assume left-to-right text direction
11. Report all findings with file paths and line numbers

1. For extract:
2. Scan all source files for localized string references
3. Compare against the existing string table (if any) in assets/data/
4. Generate new entries for strings that don't have keys yet
5. Suggest key names following the convention: [category].[subcategory].[description]
6. Output a diff of new strings to add to the string table

1. For validate:
2. Read all string table files in assets/data/
3. Check each entry for:
4. Missing translations (key exists but no translation for a locale)
5. Placeholder mismatches (source has {name} but translation is missing it)
6. String length violations (exceeds character limits for UI elements)
7. Orphaned keys (translation exists but nothing references the key in code)
8. Report validation results grouped by locale and severity

1. For status:
2. Count total localizable strings
3. Per locale: count translated, untranslated, and stale (source changed since translation)
4. Generate a coverage matrix:

```markdown ## Localization Status Generated: [Date]

| Locale | Total | Translated | Missing | Stale | Coverage | |--------|-------|-----------|---------|-------|----------| | en (source) | [N] | [N] | 0 | 0 | 100% | | [locale] | [N] | [N] | [N] | [N] | [X]% |

### Issues

• [N] hardcoded strings found in source code
• [N] strings exceeding character limits
• [N] placeholder mismatches
• [N] orphaned keys (can be cleaned up)

```

Rules

• English (en) is always the source locale
• Every string table entry must include a translator comment explaining context
• Never modify translation files directly — generate diffs for review
• Character limits must be defined per-UI-element and enforced automatically
• Right-to-left (RTL) language support should be considered from the start, not bolted on later