skills.rest
JunnnnyWon
JunnnnyWonCOMMUNITY
Explore all skills by this author →
GitHub

localize

Automate the end-to-end video game localization pipeline from string extraction to QA.

Updated Aug 27, 2026
Search Tags:#qa#localization#translation#l10n#strings#rtl#vo
One-click install
npx skills add https://github.com/JunnnnyWon/Codex-Game-Studios --skill localize-junnnnywon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: localize
Source: https://github.com/JunnnnyWon/Codex-Game-Studios/tree/main/.claude/skills/localize
Command: npx skills add https://github.com/JunnnnyWon/Codex-Game-Studios --skill localize-junnnnywon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

  • 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.

  • Phase 2A: Scan Mode
  • Phase 2B: Extract Mode
  • Phase 2C: Validate Mode
  • Phase 2D: Status Mode
  • Phase 2E: Brief Mode
  • Phase 2F: Cultural Review Mode
  • Phase 2G: VO Pipeline Mode
  • Phase 2H: RTL Check Mode
  • Phase 2I: Freeze Mode
  • Phase 2J: QA Mode

Phase 3: Rules and Next Steps

  • English (en) is always the source locale
  • Every string table entry must include a context field with translator notes, character limits, and placeholder meaning
  • Never modify translation files directly — generate diffs for review
  • Character limits must be defined per-UI-element and enforced in validate mode
  • String freeze must be called before sending strings to translators — never translate a moving target
  • RTL support must be designed in from the start — retrofitting RTL layout is expensive
  • Cultural review is required for any locale where the game will be sold commercially
  • VO scripts must include director notes — raw dialogue lines produce flat recordings

Quick Start

Initiate the localization workflow by extracting strings from sources and generating a translation-ready table for all target locales.

Frequently Asked Questions about localize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate the video game localization pipeline from start to finish?▼

Game localization automation extracts hardcoded strings, generates translation tables, runs cultural reviews, manages VO pipelines, checks RTL layouts, and executes QA sign-offs. This end-to-end workflow scales across multiple locales with centralized guardrails.

When do I need to run an RTL layout check for my game translation?▼

RTL layout checks are needed when localizing for right-to-left languages, validating layout mirroring and font support. Retrofitting RTL layout is expensive, so support must be designed from the start rather than added after translation.

What is the best way to prevent translators from working on unstable game strings?▼

Enforce a string freeze to lock source strings before sending translation tables to external teams. Never translate a moving target; locking strings ensures translators work with finalized text and prevents integration errors.

Does cultural review flag sensitive game content before releasing in foreign regions?▼

Cultural review flags sensitive content, symbols, colours, and idioms that may cause issues in target locales. It is required for any locale where the game will be sold commercially to ensure native player reception.

How do I validate game translations for completeness and UI character limits?▼

Translation validation checks completeness, placeholder accuracy, and length against per-UI-element character limits. Character limits must be defined per UI element and enforced during validation to prevent text overflow in the interface.

Can I generate briefing documents for external voice-over recording teams?▼

VO pipeline management generates voice-over scripts and recording specifications for external teams. Scripts must include director notes because raw dialogue lines produce flat recordings without proper context.

Related Skills

Explore More Content & Communication Skills→
tranhieutttranhieutt
70

localize

Scan source files for hardcoded strings and localization anti-patterns.

Community
Advanced
nuoyanruoshuinuoyanruoshui
47

localize

Coordinate game localization workflows to extract, validate, and QA localizable content.

Community
Advanced
sumilee-pcusumilee-pcu

localize

Manage game localization lifecycle from string extraction to VO pipeline integration.

Community
Advanced
CharlesWiltgenCharlesWiltgen
1.1k

localization

Manage and apply String Catalogs for Xcode 15+ app localization.

Community
Intermediate