translation
kostja94/marketing-skills
Manage translation workflows, glossaries, and quality for multilingual content.
What is translation?
This skill guides translation workflow, terminology management, style guides, and quality assurance for multilingual content. Use it when translating product UI, marketing copy, blogs, landing pages, or technical docs, and when deciding between human and machine translation approaches.
- Create translator briefs with context, audience, tone, glossary, and style guide references
- Build and maintain glossaries with source terms, target translations, context, and market-specific terminology
- Define per-language style guides covering voice, tone, register, punctuation, and formatting
- Assess when to use human translation vs machine translation (MT) or machine translation post-editing (MTPE)
- Perform quality assurance checks including glossary consistency, style guide compliance, localization of numbers/dates/units, and native speaker review
- Optimize translated content for SEO by re-researching keywords in target languages rather than translating source keywords
How to install translation
npx skills add https://github.com/kostja94/marketing-skills --skill translationHow to use translation
- 1.Assess project context by checking for existing brand voice, target markets, and product terminology in project files
- 2.Identify content type (UI, marketing, blog, landing page, docs), target languages, and existing glossaries or translation memory
- 3.Create a translator brief including context, audience, tone, glossary link, style guide reference, and constraints (character limits, SEO keywords)
- 4.Build or update a glossary with source terms, target translations, context notes, and market-specific terminology
- 5.Define a per-language style guide covering voice, tone, register, punctuation, formatting, and forbidden terms
- 6.Decide on human translation, machine translation, or MTPE based on content type and stakes
- 7.Conduct quality assurance using the checklist: glossary consistency, style guide compliance, localization of numbers/dates/units, character limits, and native speaker review
- 8.Re-research keywords in target languages for SEO rather than translating keyword lists from source content
Use cases
- Translating product UI strings with strict terminology consistency using a glossary and translation memory
- Creating marketing copy for a new regional market with culturally adapted tone and tested CTAs
- Establishing a translation workflow and style guide for technical documentation across multiple languages
- Post-editing machine-translated internal documents to ensure brand voice and accuracy
- Managing market-specific terminology (e.g., AIGC for China vs Generative AI for English-speaking markets)
- Product managers localizing UI and features across markets
- Marketing teams creating multilingual campaigns and landing pages
- Content strategists managing translation workflows for blogs and documentation
- Localization managers overseeing glossaries, style guides, and translation quality
- Technical writers preparing docs for translation in multiple languages
translation FAQ
Use human translation for product UI, marketing copy, landing pages, legal content, and brand-critical materials. Machine translation may be acceptable for high-volume low-stakes content (internal docs, user-generated content) or as a draft for post-editing (MTPE). Avoid raw MT for customer-facing product and marketing content due to terminology errors and cultural misfires.
A translator brief must include: context (what the content is for), target audience and user persona, desired tone, a link to or copy of the glossary, style guide reference or key rules, and any constraints like character limits for UI or SEO keywords to include naturally.
Research how the target market actually searches and speaks rather than translating terminology lists. For example, use AIGC (人工智能生成内容) for China and Generative AI for English markets, or KOL (关键意见领袖) for Chinese marketing instead of translating 'influencer.' Document approved terms in your glossary with context notes.
A translation memory (TM) stores approved source-to-target sentence pairs for consistency and reuse. Use TM to maintain consistency across content, reduce costs per word, and accelerate turnaround. Keep it aligned with your glossary and clean of duplicates. A Translation Management System (TMS) centralizes TM, glossary, and workflow for multiple languages and team collaboration.
Re-research keywords in the target language rather than translating keyword lists from the source language. Translate metadata (title tags, meta descriptions) and ensure hreflang implementation (handled by localization-strategy skill). Avoid publishing many low-quality translated pages at once, as this can trigger search engine penalties.
Full instructions (SKILL.md)
Source of truth, from kostja94/marketing-skills.
name: translation description: When the user wants to translate content, create translation workflows, manage terminology, or optimize translation quality. Also use when the user mentions "translate," "translation," "localization copy," "glossary," "terminology," "style guide translation," "machine translation," "human translation," "TMS," or "multilingual content." For strategy, use localization-strategy. metadata: version: 1.0.1
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:
- Content type: Product UI, marketing copy, blog, landing page, docs
- Target language(s): Priority locales
- 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 + TM when available | Draft translation |
| Review | Native speaker review; consistency, brand voice, SEO | Final translation |
Translator Brief
Include in every project:
- Context: What the content is for (landing page, product UI, blog)
- Audience: Target market, user persona
- Tone: Formal, casual, technical
- Glossary: Link or attach; mandatory terms
- Style guide: Reference or key rules
- Constraints: Character limits (UI), SEO keywords to include naturally
Content-Type Workflow
| Content Type | Approach | Notes |
|---|---|---|
| Product UI | Glossary-critical; short strings; consistency | Use TM; avoid machine translation |
| Marketing copy | Brand voice; cultural adaptation | Human translation; see terminology |
| Blog / Article | SEO; natural keyword placement | Re-research keywords in target language; don't translate keyword lists |
| Landing page | Conversion-focused; CTA clarity | Human; test localized CTAs |
| Technical docs | Precision; glossary | TM + glossary; consider MT + post-edit for high volume |
2. Glossary & Terminology
Glossary Purpose
- Consistency: Same term translated the same way across all content
- Brand: Product names, feature names, approved phrasing
- Compliance: Safety, legal, regulated terms
- Cost: Reduces rework; accelerates review
Glossary Structure
| Field | Purpose |
|---|---|
| Source term | Original (e.g., English) |
| Target term | Approved translation |
| Context | Where it appears; usage note |
| Do not translate | Brand names, product names (when applicable) |
Market-Specific Terminology
| Term | English | Chinese | Notes |
|---|---|---|---|
| Generative AI | Generative AI, GenAI | AIGC (人工智能生成内容) | Use "AIGC" for China; "Generative AI" for English |
| Influencer | Influencer | KOL (关键意见领袖) | "KOL" common in Chinese marketing |
| User | User | 用户 | Context-dependent |
| Dashboard | Dashboard | 控制台, 仪表盘 | Choose one; document in glossary |
Principle: Don't translate terminology lists; research how target market searches and speaks. See keyword-research for multi-language keyword research.
3. Style Guide (Translation)
Elements to Define
| Element | Purpose |
|---|---|
| Voice | Brand personality; formal vs casual |
| Tone | Varies by content type (support = helpful; marketing = persuasive) |
| Register | Formal (您) vs informal (你) in languages that distinguish |
| Punctuation | Quotation marks, spacing (e.g., no space before colon in French) |
| Formatting | Dates, numbers, units; locale-specific |
| Forbidden | Terms or phrases to avoid |
Per-Language Considerations
- Chinese: Simplified vs Traditional; measure word usage
- German: Formal (Sie) vs informal (du); compound nouns
- Japanese: Honorifics; keigo for formal contexts
- Arabic: RTL; formal vs dialect
4. Human vs Machine Translation
When to Use Human Translation
| Scenario | Reason |
|---|---|
| Product UI | Terminology, UX clarity, brand |
| Marketing copy | Persuasion, cultural nuance, CTAs |
| Landing pages | Conversion; tested copy |
| Legal, compliance | Accuracy, liability |
| Brand-critical | Taglines, campaign copy |
When Machine Translation (MT) May Be Acceptable
| Scenario | Condition |
|---|---|
| High-volume, low-stakes | Internal docs, user-generated content |
| Draft / triage | MT + human post-edit (MTPE) |
| Real-time | Chat, support; with disclaimer |
Avoid
- Raw MT for product/marketing: Terminology errors, cultural misfires, poor SEO
- MT without post-edit for customer-facing content
- Translating keyword lists instead of re-researching in target language
5. Translation Memory (TM) & TMS
Translation Memory
- What: Stores approved source↔target sentence pairs
- Benefit: Consistency; reuse; lower cost per word; faster turnaround
- Best practice: Maintain TM; clean duplicates; align with glossary
Translation Management System (TMS)
- Use for: Centralized workflow; glossary + TM integration; vendor management
- When: Multiple languages; ongoing translation; team collaboration
6. Quality & SEO
Quality Checklist
- Glossary terms used correctly
- Style guide followed
- No untranslated strings
- Numbers, dates, units localized
- Character limits respected (UI)
- Native speaker review completed
SEO for Translated Content
- Keywords: Re-research in target language; don't translate from source
- Metadata: Title, description translated; see title-tag, meta-description
- Hreflang: Technical implementation in localization-strategy; translation produces the content
- Thin content: Avoid publishing many low-quality translated pages at once; can trigger penalties. See localization-strategy Multilingual Risks.
7. Integration with Localization
| Topic | Skill |
|---|---|
| i18n implementation | localization-strategy |
| URL structure, hreflang | localization-strategy |
| Translation workflow, glossary, style | This skill (translation) |
| Keyword research by market | keyword-research; localization-strategy |
When adding a new locale: create glossary, style guide, then translate. See localization-strategy for technical checklist (hreflang, sitemap, metadata).
Output Format
- Translator brief (context, audience, glossary, style)
- Glossary additions or updates
- Style guide notes for target language
- Human vs MT recommendation
- Quality checklist
Related Skills
Strategy & Technical
- localization-strategy: i18n, hreflang, URL structure, pricing by market; translation produces content for localized pages
- content-strategy: Multilingual content planning; avoid thin translations
- content-marketing: Content types and formats; translation as one channel adaptation
SEO & Content
- keyword-research: Multi-language keyword research; don't translate keyword lists
- page-metadata: Hreflang implementation
- title-tag, meta-description: Translate metadata per locale
- copywriting: Source copy to translate; brand voice
- image-optimization: Localize image filenames for translated pages
Pages
- article-page-generator: Article structure; translate with SEO in mind
- landing-page-generator: Landing page copy; human translation for conversion
Related skills
More from kostja94/marketing-skills and the wider catalog.
trust-badges-generator
When the user wants to add or optimize trust badges, "Trusted by" logos, security seals, or social proof elements. Also use when the user mentions "trust badges," "trusted by," "security badges," "payment logos," "social proof," "trust seals," "SSL badge," "customer logos," "as seen in," or "trust signals." For press logos, use press-coverage-page-generator.
twitter-cards
When the user wants to add or optimize Twitter Card metadata for X (Twitter) link previews. Also use when the user mentions "Twitter Card," "twitter:card," "twitter:image," "twitter:title," "X preview," or "tweet preview." For Facebook/LinkedIn previews, use open-graph.
twitter-x-posts
Generate publish-ready X (Twitter) posts, threads, and optimized copy for maximum engagement.
url-slug-generator
When the user wants to create, optimize, or validate URL slugs for content pages. Also use when the user mentions "URL slug," "URL path," "blog URL," "article URL," "short URL," "clean slug," "permalink," "slug optimization," "URL structure," "SEO-friendly URL," "create URL slug," or "SEO slug." For site-wide URL policy, use url-structure.
url-structure
When the user wants to optimize URL structure, fix URL issues, or plan URL hierarchy. Also use when the user mentions "URL structure," "URL optimization," "slug," "clean URLs," "URL hierarchy," "URL path," "permalink structure," "URL best practices," "dynamic URLs," or "URL parameters." For per-page slug wording, use url-slug-generator. For canonical consolidation, use canonical-tag.
use-cases-page-generator
When the user wants to create, optimize, or audit use case pages. Also use when the user mentions "use cases," "use case page," "for [role]," "by persona," "by scenario," "by business goal," "ICP pages," or "audience-specific pages." For sitewide page planning, use website-structure.