Verified:GitHub

localize

Scan game source code for hardcoded strings and generate translation-ready string tables.

Updated May 13, 2026

Search Tags:#localization #string extraction #string freeze #cultural review #translation validation #RTL testing #VO integration

Ready to run

npx skills add https://github.com/FrancisVarga/the-dream-machine --skill localize-francisvarga

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: localize
Source: https://github.com/FrancisVarga/the-dream-machine/tree/main/.claude/skills/localize
Command: npx skills add https://github.com/FrancisVarga/the-dream-machine --skill localize-francisvarga

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Glob, Grep, Bash, Task, AskUserQuestion, and includes assets (resource) components.

What problem does it solve?

Localization projects fail when hardcoded text, missing placeholders, cultural issues, or RTL layout problems slip through late, causing rework and risking release or certification delays.

Core Features & Use Cases

End-to-end localization pipeline: scan for hardcoded strings, extract and manage string tables, validate translations, and run QA sign-off.
Translation-ready outputs: generates translator briefings and structured artifacts for external/local teams.
Release safety gates: enforces string freeze/violations, checks placeholders and formatting, and verifies RTL and VO integration needs.
Cultural and sensitivity review: flags symbols, colors, humor, numbers, names, and rating/content risks across locales.

Quick Start

Run the localization pipeline in scan mode to find hardcoded user-facing strings in the game's source code by calling /localize scan.

Frequently Asked Questions about localize

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

FAQPage Schema

How do I find hardcoded strings in game source code for localization?▼

To find hardcoded strings for localization, run a source code scan to detect user-facing text and automatically generate translation-ready string tables. This process identifies unextracted text and outputs structured artifacts for external translation teams.

How do I enforce a string freeze during game release QA?▼

You can enforce a string freeze by scanning the codebase to detect post-freeze modifications to string tables. The system validates placeholder integrity and flags violations, ensuring release safety by preventing untracked text changes from delaying certification.

Can I validate translation placeholders and RTL layout for different locales?▼

Yes, translation validation includes checking placeholder formatting and running RTL layout checks across locales. The system flags missing translations, formatting mismatches, and layout risks to ensure cultural and technical readiness before release.

Does the localization pipeline support cultural sensitivity reviews?▼

The localization pipeline supports cultural sensitivity reviews by flagging symbols, colors, humor, numbers, names, and rating risks across locales. This identifies content issues early, preventing rework and ensuring regional compliance before release.

What is the best way to prepare VO integration for localized game audio?▼

Preparing VO integration involves extracting translation-ready string tables and generating structured artifacts for voice-over pipelines. The system validates text completeness and formatting to ensure localized audio matches the final string freeze.

Can I use Bash and Grep to extract translation-ready string tables?▼

Yes, the pipeline uses Bash, Grep, and Glob dependencies to scan source files and extract translation-ready string tables. These tools automate the identification of hardcoded text and output structured reports for downstream localization.