localize

Scan source code for hardcoded strings and generate localization string tables.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/dnkrow/skill --skill localize-dnkrow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localize
Source: https://github.com/dnkrow/skill/tree/main/claude-global/localize
Command: npx skills add https://github.com/dnkrow/skill --skill localize-dnkrow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

This Skill turns localization into a controlled, repeatable pipeline so you can find hardcoded strings, manage translation tables, reduce placeholder and formatting bugs, and ship locale-ready builds with culturally appropriate content.

Core Features & Use Cases

  • Localization scanning: Detect hardcoded user-facing strings and common i18n anti-patterns across source code.
  • String table extraction & generation: Create new keyed entries with translator context from source usage, then output reviewable diffs for updating the English table.
  • Translation validation, coverage, and QA: Check completeness, placeholders, length/context constraints, freeze violations, and produce a structured playthrough QA verdict per locale.
  • Localization-specific workflows: Cultural/sensitivity review, RTL layout checks, and VO pipeline planning/validation/integration.

Quick Start

Run localize extract to scan your source and propose new localization string-table entries with translator context.

Frequently Asked Questions about localize

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

FAQPage Schema
How do I scan source code to find hardcoded strings for game localization?

Game localization scanning detects hardcoded user-facing strings and common i18n anti-patterns across source code. Running an extraction command scans the codebase to propose new keyed string-table entries complete with translator context.

What is the best way to validate translation string tables and check placeholder coverage?

Translation validation checks string table completeness, named placeholders, length constraints, and freeze violations. It produces a structured QA verdict per locale to ensure translation-ready content meets schema conventions before integration.

Does this localization workflow support RTL layout checks and cultural sensitivity reviews?

Yes, the localization workflow supports locale-specific QA including RTL layout checks and cultural sensitivity reviews. These features ensure multi-locale game builds ship with culturally appropriate content and correct right-to-left text formatting.

How do I manage voice-over localization and VO pipeline integration for multiple locales?

Voice-over localization is managed through VO pipeline planning, validation, and integration tasks. The workflow processes VO assets alongside string tables to ensure audio and text localization remain synchronized across multi-locale builds.

Can I use this to extract translation-ready string tables from an English source locale project?

Yes, this works with multi-locale projects using English as the source locale. The extraction process scans source usage to generate keyed entries with translator context, outputting reviewable diffs for updating the English string table.

What are common i18n anti-patterns that break game localization, and how do I avoid them?

Common i18n anti-patterns include hardcoded user-facing strings, unnamed placeholders, and missing translator context fields. The localization scanner detects these issues and enforces schema conventions to produce valid, translation-ready string tables.