localize

Orchestrate an end-to-end game localization pipeline from scan to QA.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/solace-ill/vector-flow --skill localize-solace-ill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localize
Source: https://github.com/solace-ill/vector-flow/tree/main/.claude/skills/localize
Command: npx skills add https://github.com/solace-ill/vector-flow --skill localize-solace-ill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The localization pipeline coordinates the full lifecycle of localizing game content for global markets, including scanning for hardcoded strings, extracting translation keys, managing translator briefs, validating translations, conducting cultural and RTL reviews, coordinating VO localization, enforcing string freezes, and executing QA to ensure locale readiness.

Core Features & Use Cases

  • End-to-end workflow covering scan, extract, validate, brief, cultural-review, vo-pipeline, rtl-check, freeze, and qa.
  • Role-based collaboration with task assignments, status tracking, and tool integration across locales.
  • Use Case: A studio localizes a new build by generating translation keys, producing briefs, validating translations, performing cultural checks, and delivering QA-ready assets.

Quick Start

Run the /localize workflow to process a fresh build through scan, extract, validate, and QA.

Frequently Asked Questions about localize

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

FAQPage Schema
What is an end-to-end localization pipeline for game content?

An end-to-end localization pipeline orchestrates scan, extract, validate, brief, cultural-review, vo-pipeline, rtl-check, freeze, and qa stages for multi-language games. It ensures production readiness by managing translation workflows and QA traceability across platforms and regions.

How do I automate translation key extraction and hardcoded string scanning?

Automate string scanning and key extraction by running the localization workflow on a fresh build. This process identifies hardcoded strings and generates translation keys to initiate the translation workflow with traceable outputs.

Does this localization workflow support RTL checks and cultural reviews?

Yes, the localization workflow includes dedicated cultural-review and rtl-check stages. These validate translations for regional appropriateness and right-to-left script accuracy to ensure locale readiness before enforcing string freezes.

How do I generate context-rich translator briefs with placeholder handling?

Generate context-rich translator briefs during the brief stage of the localization pipeline. This stage provides translator guidance and handles placeholders alongside character limits to ensure accurate translation validation.

Can I use this pipeline for multi-language game updates across different platforms?

Yes, the pipeline applies to multi-language games across platforms and regions. It handles new content updates and ongoing localization cycles, coordinating role-based collaboration and tool integration to deliver QA-ready assets.