Translator AI Skill
Use this skill to produce meaning-first translations, translation rewrites, and localization passes for product copy, technical documentation, UI strings, emails, and general business writing.
Treat English to Turkish as the highest-confidence path in this repository. Treat English to Spanish, French, and German as structured secondary coverage with starter rules and examples. Treat Portuguese, Italian, and Russian material as exploratory reference support until native-speaker review is documented.
Quick Proof
English: Stop leaving money on the table.
Literal Turkish: Masada para bırakmayı durdurun.
Meaning-first Turkish: Gözünüzün önündeki fırsatları kaçırmayın.
Use that standard for every pair: preserve the message and the effect, not the surface wording.
Use This Skill For
- Translate English text while preserving tone, intent, and formatting.
- Review an existing translation and make it sound native.
- Localize marketing copy or UI text for a target audience.
- Explain non-obvious translation choices when detailed output is requested.
- Adapt idioms, humor, formality, and culture-bound phrasing.
Quick Prompt Patterns
Translate to Turkish: [text]
Translate to Turkish (detailed): [text]
Localize this landing page copy for Turkish users: [text]
Review this Turkish translation and make it sound native: [text]
Translate to Spanish (draft): [text]
Scope and Confidence
| Language pair | Status | Guidance |
|---|---|---|
| English to Turkish | Primary | Use full workflow and checklist. Best path for public-facing work in this repo. |
| English to Spanish/French/German | Structured secondary | Use for drafts and guided localization. Recommend human review before publishing. |
| English to Portuguese/Italian/Russian | Experimental reference | Use as a starting point only. Do not present as fully validated. |
Workflow
- Read the entire source before translating. Identify audience, purpose, and tone.
- Classify the text: technical, marketing, casual, formal, creative, or mixed.
- Choose the target language, desired formality, and output mode.
- Load reference material as needed:
references/translation-rules.mdfor pair-level rulesreferences/special-cases.mdfor idioms, humor, cultural references, and addressingreferences/quality-checklist.mdfor post-translation QAreferences/examples.mdfor worked examplesreferences/language-pair-quality-matrix.mdfor current support level
- Translate for meaning first. Rewrite phrases when literal wording harms clarity, tone, or naturalness.
- Run the checklist before delivering. Verify meaning, tone, consistency, and formatting.
- Deliver clean output by default. Include notes only when requested or when ambiguity affects the result.
Output Modes
Standard Translation
Return only the translated text with formatting preserved.
Detailed Translation
Return the translation plus a short note covering:
- text category
- formality choice
- key idiom or terminology decisions
- any ambiguity worth flagging
Review Mode
When the user provides an existing translation, do this:
- Evaluate meaning drift, awkward phrasing, tone mismatch, and consistency issues.
- Rewrite the translation.
- Summarize the fixes in a few bullets if requested.
Localization Mode
When the user asks to localize rather than translate literally, do this:
- Preserve the message and CTA.
- Adapt idioms, references, and formality for the target audience.
- Avoid adding market claims or factual content not present in the source.
Core Rules
- Prefer meaning over words.
- Prefer native phrasing over mirrored English syntax.
- Preserve the original tone unless the user asks for a rewrite.
- Keep structure intact: headings, lists, tables, links, and code blocks.
- Add nothing that is not in the source.
- Omit nothing that changes meaning.
Human Review Triggers
Escalate to human or native-speaker review when any of these apply:
- public-facing copy in a non-primary language pair
- legal, medical, financial, or contractual text
- region-specific campaigns where variant choice matters
- humor or wordplay that depends on local culture
- certified translation requirements
Reference Files
references/translation-rules.md- Pair-specific rules and grammar guidancereferences/special-cases.md- Idioms, humor, cultural references, numbers, and addressingreferences/quality-checklist.md- Reusable QA checklist for translation and review workreferences/examples.md- Reviewed Turkish examples plus starter examples for secondary pairsreferences/examples-100-complete.md- Large English/Turkish prompt corpus for breadth and edge casesreferences/language-pair-quality-matrix.md- Honest support matrix and upgrade pathreferences/grammar-comparison.md- Cross-language grammar notesreferences/false-friends.md- High-risk misleading lookalikesreferences/common-mistakes.md- Failure patterns to avoid
Delivery Standard
Aim for translations that read like original writing in the target language, not like polished machine output. Keep the final answer concise, preserve the user's structure, and surface reasoning only when it materially helps.