localize

Manage game localization workflows from string extraction to release readiness.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/scomofo/dragon-forge --skill localize-scomofo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localize
Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/localize
Command: npx skills add https://github.com/scomofo/dragon-forge --skill localize-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Game localization fails when teams only translate text but skip string discovery, placeholder validation, cultural/RTL review, VO preparation, and QA sign-off—leading to broken UI, mistranslations, and certification risk.

Core Features & Use Cases

  • Localization pipeline coverage: scan, extract, validate, track status, and run full QA before release.
  • Translator-ready deliverables: generate translator briefings and cultural/sensitivity review reports with actionable findings.
  • VO and platform readiness: manage voice-over localization scripts and validate audio integration, including RTL/platform checks and string-freeze enforcement.

Quick Start

Use the localize skill in extract mode to generate translation-ready string table diffs for your project’s current English source.

Frequently Asked Questions about localize

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

FAQPage Schema
How do I extract UI text strings from Godot source code for game localization?

Game localization string extraction scans Godot source code to discover and extract keyed UI strings, generating deterministic translation-ready string table diffs. This process ensures all translatable text is captured and validated with placeholder and context checks before translator handoff.

What is a string freeze and how does it enforce localization QA gates?

A string freeze halts source text changes to enforce localization QA gates for each locale, ensuring translators and QA testers work against stable string tables. This prevents integration failures and UI breakage caused by late text modifications during release readiness.

Can I use this to generate translator briefings and cultural sensitivity review reports?

Yes, this workflow generates translator-ready deliverables including translator briefings and cultural sensitivity review reports with actionable findings. These outputs provide translators with necessary context and flag potential cultural issues before translation begins.

How do I validate RTL layout and platform readiness for localized game UI?

RTL and platform layout verification checks localized UI text rendering for right-to-left languages and platform-specific certification requirements. This validates string tables and audio integration to prevent UI overflow and certification risks across different locales.

Does this support VO pipeline coordination for voice-over localization scripts?

Yes, the workflow manages voice-over localization scripts and validates audio integration as part of VO pipeline coordination. This ensures voice acting assets are properly localized, tracked, and integrated alongside text string tables for each locale.

What is the best way to report locale coverage during game translation QA?

Locale coverage reporting tracks translation status across all target languages by validating keyed strings against string tables. This generates deterministic outputs showing completion percentages and missing translations to ensure full release readiness before sign-off.