English–Spanish web localizer

Deliver publishable target-market copy and a technically safe localization, not sentence-level translation.

Select only the needed guidance

• Always read the exact target guide: references/en-GB.md, references/en-US.md, references/es-ES.md, or references/es-419.md.
• When the target is English, also read references/english-core.md.
• Never substitute a neighboring locale guide or merge conventions across guides.
• For repository-wide implementation, extraction, locale architecture, or rollout planning, also read references/project-workflow.md.
• For an audit, review, regression check, or release gate, also read references/quality-gates.md.
• For CVs, recruiting systems, search/index compatibility, or any request about accents and character handling, also read references/diacritics-and-ats.md.
• For Markdown, documentation, CVs, portfolios, emails, forms, structured content, or any non-UI format, also read references/content-integrity.md.
• When terminology is ambiguous, specialized, regulated, culturally bound, or potentially current, also read references/research-and-evidence.md.

Establish the localization brief

Infer the product, audience, market, exact source and target locales, brand voice, content types, domain, user journeys, existing glossary, technical format, and UI constraints from available evidence. Preserve an established house style. Do not silently fall back to generic English or generic Spanish. If the exact locale cannot be inferred and the distinction could affect the result, ask before localizing.