Switch game localization

Deliver a reproducible, source-validated localization patch for the requested game, version and language. This is an engineering and editorial workflow, not a universal game converter. Vietnamese is a supported workflow, not an assumed target when the user requests another language.

Establish the project

Recover existing project notes and authorization before starting over. Identify the game, application title ID, region, installed version, source/target language, language slot to replace, engine/runtime, available extracted files, and console/mod environment. Ask only for consequential missing facts; inspect accessible files first. Treat archive filenames as hints, not authoritative title IDs.

Record a project configuration and source manifest using project structure. Keep originals immutable and keep work-in-progress, reviewed translation and release folders separate. If extraction is needed, read private inputs and extraction, then use the user's own available game dump and local tools appropriate to its format. Keep keys and console-unique data outside reports, logs, skills and release archives; request paths rather than key contents. A RomFS-only project may be enough until executable analysis is actually needed.

Optional read-only inventory helper:

Bundled helpers require Python 3.9+ and only its standard library. Commands below are relative to this skill's directory; resolve the script path there and pass the actual project paths, rather than changing or guessing the project's root.

python3 scripts/inventory_assets.py /path/to/extracted/romfs --output /path/to/project/research/inventory.json

Add --hash when a complete input hash inventory is useful. This recognizes signatures and extensions as clues, not proof of the engine or active language assets. For new tool/firmware combinations, consult current official upstream documentation rather than assuming this project's historical versions still apply.