Context first.
Care at every stage.

Establish the exact build, available source material, permissions, and delivery scope before work begins.

Understand the narrative structure, interface text, file formats, and technical constraints. Identify what can be translated and what must remain unchanged.

Research character voices, recurring concepts, cultural references, and existing terminology so choices are grounded in the game.

Separate translatable text from code and control syntax, preserving identifiers and the information needed for reintegration.

Localize into natural Latin American Spanish, then review meaning, tone, grammar, and character voice. AI-assisted tools may support the workflow; context and editorial review remain essential.

Check recurring terms, names, forms of address, omitted text, and references across scenes rather than treating every line in isolation.

Adapt menus and authorized text-bearing assets within the agreed scope. Account for length, readability, visual hierarchy, and the space available.

Check supported file structures, variables, placeholders, tags, and other protected elements. Static validation is not the same as running the game.

Reinsert localized content into the agreed format and document the delivery, known limitations, and any checks still needed in the game.

Compare new material with the previous version, preserve sound decisions, and review changed context as the game evolves.