localize

Extract and validate game localization strings across multiple locales.

23.7k|3.4k|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/Donchitos/Claude-Code-Game-Studios --skill localize-donchitos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localize
Source: https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/localize
Command: npx skills add https://github.com/Donchitos/Claude-Code-Game-Studios --skill localize-donchitos

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the complex and error-prone process of managing game localization, ensuring consistency and reducing the risk of hardcoded text or translation errors.

Core Features & Use Cases

  • String Extraction: Automatically identifies and extracts user-facing strings from source code.
  • Validation: Checks for missing translations, placeholder mismatches, and adherence to character limits.
  • Status Reporting: Provides a clear overview of localization coverage and potential issues.
  • Use Case: Integrate this Skill into your development pipeline to ensure all in-game text is properly prepared for translation into multiple languages, preventing costly mistakes before release.

Quick Start

Use the localize skill to scan for hardcoded strings in the source code.

Frequently Asked Questions about localize

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

FAQPage Schema
How do I extract hardcoded strings from game source code for localization?

Game localization string extraction is automated by scanning source code to identify hardcoded text and generate structured string tables. This process ensures all user-facing text is properly prepared for internationalization and translation management.

What is game localization validation and how does placeholder mismatch checking work?

Game localization validation checks for missing translations, placeholder mismatches, and character limit violations across multiple locales. It scans generated string tables to ensure translation consistency and adherence to internationalization best practices.

Can I integrate string extraction and translation management into my game development pipeline?

Yes, you can integrate this localization workflow into your game development pipeline to scan source code, validate translations, and report status. It prevents costly translation errors and hardcoded text issues before release.

What's the best way to track localization coverage and missing translations across multiple locales?

Tracking localization coverage is handled through status reporting, which provides a clear overview of translation completion and potential issues across multiple locales. It identifies missing translations and placeholder mismatches automatically.

Why does internationalization fail when hardcoded text is not extracted into string tables?

Internationalization fails because hardcoded text in source code cannot be translated or managed across multiple locales. Extracting strings into string tables ensures all user-facing text is properly identified and prepared for translation workflows.