localize

Scan game source code for hardcoded strings and extract localization keys.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nevesb/idol-agency-maker --skill localize-nevesb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localize
Source: https://github.com/nevesb/idol-agency-maker/tree/main/.claude/skills/localize
Command: npx skills add https://github.com/nevesb/idol-agency-maker --skill localize-nevesb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Localization is more than translation; it prevents hardcoded strings, inconsistent translations, UI breakage, cultural missteps, and failed platform certifications by providing a repeatable end-to-end process for preparing a game for multiple locales.

Core Features & Use Cases

  • Scan source code to find hardcoded user-facing strings and localization anti-patterns.
  • Extract strings into translation-ready tables and generate diffs with contextual translator notes and character limits.
  • Validate translations across locales for completeness, placeholder correctness, plural forms, encoding, and coverage metrics.
  • Produce translator briefs, run cultural sensitivity reviews, manage VO recording and integration, perform RTL layout checks, enforce string freeze policies, and run a structured localization QA pass before release.

Quick Start

Run a scan of the codebase to produce a list of hardcoded strings and then extract new keys into the project's string table for review.

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 before localization?

Scanning source code for hardcoded user-facing strings is the first step in game localization. A pipeline scan detects anti-patterns and extracts new keys into translation-ready string tables for review.

What does a full game localization pipeline include beyond translation?

A full game localization pipeline includes string extraction, cultural review, voice-over manifest generation, RTL layout verification, placeholder validation, and structured QA passes before release.

How do I extract strings into translation-ready tables with context for translators?

String extraction pulls user-facing text into tables and generates diffs with contextual translator notes and character limits. This ensures translators receive necessary context for accurate localization.

Can I validate translations for placeholder correctness and plural forms across locales?

Translation validation checks completeness, placeholder correctness, plural forms, encoding, and coverage metrics across all locales. This catches formatting errors before strings reach the QA stage.

What is the best way to handle RTL layout verification and cultural review for game locales?

RTL layout verification and cultural sensitivity reviews are part of a structured localization pipeline. Running these checks alongside VO manifest generation and string freeze enforcement prevents UI breakage and cultural missteps.

Do I need read access to source code and design documents to run localization automation?

Yes, localization automation requires read access to src/, assets/data/strings/, and design documents. It writes localization reports, briefs, and manifest files for QA and vendor handoff.