translation

# Content: Translation Guides translation workflow, terminology, style, and quality for multilingual content. Covers when to use human vs machine translation, glossary and style guide creation, and SEO considerations. For i18n implementation, hreflang, and URL structure, see **localization-strategy**. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Scope - **Workflow**: Brief → translate → review - **Terminology**: Glossary creation and management - **Style guide**: Voice, tone, formatting per language - **Human vs MT**: When to use each; post-editing - **Quality**: QA, consistency, SEO - **Market-specific**: Terminology by region ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for brand voice, target markets, and product terminology. Identify: 1. **Content type**: Product UI, marketing copy, blog, landing page, docs 2. **Target language(s)**: Priority locales 3. **Existing assets**: Glossary, style guide, translation memory (TM) --- ## 1. Translation Workflow ### Brief → Translate → Review | Phase | Purpose | Output | |-------|---------|--------| | **Brief** | Context, audience, tone, glossary reference, style guide | Translator brief document | | **Translate** | First pass; use glossary +...