!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation

Localization Pipeline

Localization is not just translation, it is the full process of making a game feel native in every language and region. Poor localization breaks immersion, confuses players, and blocks platform certification. This skill covers the complete pipeline from string extraction through cultural review, VO recording, RTL layout testing, and localization QA sign-off.

Modes:

• scan, Find hardcoded strings and localization anti-patterns (read-only)
• extract, Extract strings and generate translation-ready tables
• validate, Check translations for completeness, placeholders, and length
• status, Coverage matrix across all locales
• brief, Generate translator context briefing document for an external team
• cultural-review, Flag culturally sensitive content, symbols, colours, idioms
• vo-pipeline, Manage voice-over localization: scripts, recording specs, integration
• rtl-check, Validate RTL language layout, mirroring, and font support
• freeze, Enforce string freeze; lock source strings before translation begins
• qa, Run the full localization QA cycle before release

If no subcommand is provided, output usage and stop. Verdict: FAIL, missing required subcommand.

---

Every AskUserQuestion call follows .claude/docs/automation-modes.md (collaborative asks always · guided major-only · autonomous logs and proceeds; automation_always_ask categories always prompt).

Phase 2A: Scan Mode

Search the code root (resolve per .claude/docs/code-root-resolution.md) for hardcoded user-facing strings. If the code root is unresolved, report NOT ASSESSED, code root unresolved rather than zero hits. Zero hits from an unresolved root reads as "nothing to localize", which is the failure this guards: