translation-expertise
Skill4 starsChanged 31 days agoISCView on GitHub
Expert translation methodology and best practices for English-Japanese-Chinese (Traditional) trilingual translation. Use when translating any content between these languages, including handling idioms, cultural nuances, and language-specific expressions. Provides translation workflows and quality assurance methods.
In this repository7 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- context-managerSkill
- dependency-updateSkill
- document-writingSkill
- engineering-terminologySkill
- security-updateSkill
- web-browsingSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
38 rules. About 0 are common, 36 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈36
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Keep framework and product names in English: React, Next.js, TanStack Query, Zustand, Zod, pnpm, PR
- Distinctive: line 28
Use the established katakana/Japanese for general concepts: コンポーネント, フック, 状態管理, デプロイ, レビュー
- Distinctive: line 34
Use 繁體中文 and Taiwan terminology by default (軟體, 網路, 資訊)
- Distinctive: line 35
Keep framework and product names in English
- Distinctive: line 37
Use 成語 sparingly and only when it reads naturally
- Distinctive: line 41
Output: write the translation in place or to the requested file.
- Very specific: line 43
Web sources: use WebFetch for simple pages.
- Distinctive: line 52
Contextual Accuracy: Consider the broader context, not just individual words
- Distinctive: line 69
Contains: All five politeness levels (plain, polite, respectful, humble, beautification) with detailed explanations, gendered speech …
- Distinctive: line 85
Read the entire source text to understand context and intent
- Distinctive: line 101
Verify sentence structure is natural in target language
- Distinctive: line 102
Check verb tenses and aspects
- Distinctive: line 103
Ensure particles (JA) or measure words (ZH) are correct
- Distinctive: line 108
Ensure consistent translation of key terms
- Distinctive: line 109
Verify technical terms are accurate
- Distinctive: line 110
Check proper nouns are handled correctly
- Distinctive: line 115
Verify idioms are culturally appropriate (see translation-challenges.md)
- Distinctive: line 116
Check for culturally sensitive content
- Distinctive: line 117
Ensure examples and analogies work in target culture
- Distinctive: line 123
Ensure formality level matches the source
- Distinctive: line 124
Verify the text flows naturally
- Distinctive: line 125
Check that emphasis and nuance are preserved
- Distinctive: line 175
Strategy: Use context clues, research, and informed judgment when source is ambiguous.
- Distinctive: line 191
Important: Use full-width punctuation for Japanese and Chinese text.
- Distinctive: line 197
Before finalizing any translation:
- Distinctive: line 236
Always Translate in Context: Never translate sentences in isolation
- Distinctive: line 237
Maintain Terminology Consistency: Use glossaries and translation memories
- Distinctive: line 238
Research Thoroughly: Look up unfamiliar terms and verify meanings
- Distinctive: line 242
Document Decisions: Keep notes on difficult translation choices
- Distinctive: line 245
Preserve Intent: When in doubt, prioritize the author's intended meaning
- Distinctive: line 299
Read entire source text first for context
- Distinctive: line 300
Create terminology glossary for consistency
- Distinctive: line 303
Verify punctuation conventions for target language
- Distinctive: line 306
Document difficult translation decisions
- Distinctive: line 310
Japanese: Use です/ます polite form unless clear context suggests otherwise
- Distinctive: line 311
Chinese: Use 您 for formal contexts, 你 for casual.
- Distinctive: line 312
Punctuation: Use「」for quotes in JA/ZH Taiwan style.
- Distinctive: line 313
Idioms: When direct equivalent unclear, prioritize conveying meaning over preserving metaphor
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Translation Expertise
Overview
This skill provides comprehensive translation expertise for English, Japanese, and Traditional Chinese. It covers translation methodologies, cultural considerations, and best practices for producing high-quality translations.
Technical Documentation in This Workspace
Most translation here is engineering content. These rules take precedence over the general guidance below.
Never translate:
- Code blocks, inline code, identifiers, file paths, commands, CLI flags, URLs, frontmatter keys
- Markup and macros (HTML, JSX, Confluence storage format) — translate only the text nodes
- Severity prefixes and verdicts in review reports (⚠️ Critical, 💡 Suggestion, ❓ Question, 💅 Nit, 🎉 Praise, APPROVE / REQUEST CHANGES / BLOCK)
Preserve structure 1:1: same heading levels and order, lists, tables, links and anchors, so an -en/-ja (or -zh) pair diffs section by section.
Japanese house style:
- です/ます form for guidelines, specs and reports — not である調
- Keep framework and product names in English: React, Next.js, TanStack Query, Zustand, Zod, pnpm, PR
- Use the established katakana/Japanese for general concepts: コンポーネント, フック, 状態管理, デプロイ, レビュー
- Headings use
日本語 (English)form, e.g.コア原則 (Core Principles) - Full-width punctuation in Japanese prose; half-width inside code and identifiers
Traditional Chinese house style:
- Use 繁體中文 and Taiwan terminology by default (軟體, 網路, 資訊)
- Keep framework and product names in English
- Full-width punctuation in prose; half-width inside code and identifiers
- Use 成語 sparingly and only when it reads naturally
Document pairs (*-en.md / *-ja.md / *-zh.md): when one side changes, update the matching sections of the other in the same change, translating from the side that changed. Don't retranslate untouched sections.
Output: write the translation in place or to the requested file; list uncertain term choices briefly at the end, not inline.
Web sources: use WebFetch for simple pages; use the agent-browser / browser-use skills for interactive or JS-heavy pages. Don't use Playwright for text extraction; it is reserved for e2e tests.
Translation Philosophy
Core Principles
- Meaning over Literalness: Convey the intended meaning rather than word-for-word translation
- Cultural Adaptation: Adapt content for the target culture while preserving the original intent
- Natural Flow: Translations should read naturally in the target language
- Contextual Accuracy: Consider the broader context, not just individual words
- Tone Preservation: Maintain the original tone (formal, casual, technical, emotional)
Language-Specific References
For comprehensive information about each language, see the dedicated language reference files:
English
Key Features: SVO word order, explicit subjects and articles, direct communication style, active voice preference.
Contains: Structural features, formality indicators (informal/formal/academic), punctuation conventions, common idioms, phrasal verbs, modal verbs, translation strategies, regional variations (US/UK).
Japanese (日本語)
Key Features: SOV word order, context-dependent subject omission, three writing systems (hiragana, katakana, kanji), elaborate honorific systems (keigo).
Contains: All five politeness levels (plain, polite, respectful, humble, beautification) with detailed explanations, gendered speech patterns, particle usage, writing system guidelines, translation strategies, cultural concepts.
Chinese Traditional (繁體中文)
Key Features: SVO word order like English, no verb conjugation, measure words (classifiers) for counting, rich idiomatic expressions (成語).
Contains: Comprehensive measure word list, regional variations (Taiwan/Hong Kong/Macau), four-character idioms (成語), formality indicators, punctuation conventions, translation strategies, terminology differences.
Quick Reference: For translation work between any language pair, open both relevant language files side-by-side for comprehensive reference.
Translation Workflow
Step 1: Initial Translation
Process:
- Read the entire source text to understand context and intent
- Identify key terminology and create a glossary
- Translate section by section, maintaining context
- Mark uncertain translations for review
Considerations:
- Understand the source culture and references
- Identify the target audience
- Determine appropriate formality level
- Note any ambiguities requiring clarification
Step 2: Proofreading & Review
Grammar and Syntax Check:
- Verify sentence structure is natural in target language
- Check verb tenses and aspects
- Ensure particles (JA) or measure words (ZH) are correct
- Validate punctuation follows target language conventions (see language-specific files)
Terminology Consistency:
- Ensure consistent translation of key terms
- Verify technical terms are accurate
- Check proper nouns are handled correctly
- Confirm units and measurements are appropriate
Cultural Adaptation:
- Verify idioms are culturally appropriate (see translation-challenges.md)
- Check for culturally sensitive content
- Ensure examples and analogies work in target culture
- Adapt humor if necessary
Tone and Style:
- Maintain consistent tone throughout
- Ensure formality level matches the source
- Verify the text flows naturally
- Check that emphasis and nuance are preserved
Step 3: Refinement Translation
Enhancement Process:
- Review feedback from proofreading
- Resolve all marked uncertainties
- Improve awkward phrasings
- Polish for naturalness and readability
- Final consistency check
Quality Markers:
- Reads naturally to native speakers
- Accurately conveys source meaning
- Maintains appropriate tone and style
- Consistent terminology throughout
- Free of grammatical errors
Common Translation Challenges
Detailed Examples: See translation-challenges.md for extensive examples with reasoning.
Challenge 1: Idioms and Expressions
Strategy: Find equivalent expressions, not word-for-word translations.
Examples: "Break a leg" → 頑張って (JA) / 加油 (ZH); "Piece of cake" → 朝飯前 (JA) / 小菜一碟 (ZH)
Challenge 2: Cultural References
Strategy: Adapt or explain references unfamiliar to target culture.
Approaches: Direct + explanation, cultural adaptation to equivalent concept, or generalization depending on context importance.
Challenge 3: Wordplay and Puns
Strategy: Recreate the effect, not the exact wordplay.
Approach: Either explain the original wordplay with translator's note, or create new language-specific wordplay that achieves similar humor effect.
Challenge 4: Formality Levels
Strategy: Match formality indicators across languages.
Key: English uses vocabulary and contractions; Japanese uses verb endings and honorifics; Chinese uses vocabulary and pronouns (你/您).
Challenge 5: Ambiguity Resolution
Strategy: Use context clues, research, and informed judgment when source is ambiguous.
Process: Analyze context, research domain-specific meanings, apply logic, choose most likely interpretation, and document reasoning.
For Detailed Examples: See translation-challenges.md for comprehensive examples with solutions.
Punctuation Quick Reference
Key Differences (See language-specific files for complete details):
- Period: . (EN) → 。(JA/ZH)
- Comma: , (EN) → 、(JA) / 、or , (ZH)
- Quotation marks: "..." (EN) →「...」(JA/ZH) or "..." (ZH alternative)
- Book titles: "..." (EN) → 『...』(JA) /《...》(ZH)
- Ellipsis: ... (EN) → …… (JA/ZH - six dots)
Important: Use full-width punctuation for Japanese and Chinese text. Maintain consistency throughout the document.
Detailed Conventions: See english.md, japanese.md, or chinese-traditional.md for complete punctuation rules.
Quality Assurance Checklist
Before finalizing any translation:
Accuracy:
- Meaning accurately conveyed
- No omissions or additions
- Numbers, dates, names correct
- Technical terms accurate
Naturalness:
- Reads fluently in target language
- No awkward phrasings
- Appropriate word choice
- Natural sentence flow
Consistency:
- Terminology used consistently
- Tone maintained throughout
- Formatting preserved
- Style guide followed
Cultural Appropriateness:
- Culturally sensitive content handled well
- Idioms adapted appropriately
- References understandable to target audience
- Examples relevant to target culture
Technical Correctness:
- Grammar correct
- Punctuation follows conventions
- Character encoding correct (UTF-8)
- No typos or errors
Best Practices
- Always Translate in Context: Never translate sentences in isolation
- Maintain Terminology Consistency: Use glossaries and translation memories
- Research Thoroughly: Look up unfamiliar terms and verify meanings
- Read Aloud: Natural translations sound good when read aloud
- Get Feedback: Have native speakers review when possible
- Iterate: First draft is rarely perfect, refinement is essential
- Document Decisions: Keep notes on difficult translation choices
- Stay Updated: Language evolves, keep learning new expressions and terms
- Know Your Limits: Flag areas requiring subject matter expertise
- Preserve Intent: When in doubt, prioritize the author's intended meaning
Tools and Resources
Comprehensive List: See tools-resources.md for detailed resources.
Essential Dictionaries:
- Jisho.org (Japanese-English)
- MDBG (Chinese-English)
- MOE Dictionary (Chinese official)
- Weblio (Japanese)
Example Sentences:
- Tatoeba (multilingual examples)
- Reverso Context (translation in context)
Grammar References:
- Tae Kim's Grammar Guide (Japanese)
- Chinese Grammar Wiki (Chinese)
- Purdue OWL (English)
Verification Tools:
- HiNative (ask native speakers)
- Google N-gram Viewer (frequency analysis)
- Reddit language communities
For Complete Resource List: See tools-resources.md for comprehensive dictionaries, corpora, grammar references, verification tools, and professional resources.
Companion Files
This skill includes the following companion documents for detailed reference:
Language-Specific References
- english.md: Complete English language reference including structural features, formality indicators, punctuation conventions, common idioms, phrasal verbs, modal verbs, and translation strategies.
- japanese.md: Complete Japanese language reference including all five politeness levels, gendered speech patterns, particle usage, writing system guidelines, and cultural concepts.
- chinese-traditional.md: Complete Traditional Chinese language reference including measure words, regional variations (Taiwan/Hong Kong/Macau), four-character idioms (成語), and formality indicators.
Cross-Language References
- translation-challenges.md: Extensive examples of common translation challenges with detailed solutions, reasoning, and multiple approaches for idioms, cultural references, wordplay, formality, and ambiguity.
- tools-resources.md: Curated list of dictionaries, corpora, grammar references, verification tools, and professional resources organized by category and language.
Quick Reference
When translating, remember:
- Read entire source text first for context
- Create terminology glossary for consistency
- Choose appropriate formality level early
- Handle idioms culturally, not literally
- Verify punctuation conventions for target language
- Proofread for naturalness and accuracy
- Get native speaker feedback when possible
- Document difficult translation decisions
Default choices when uncertain:
- Japanese: Use です/ます polite form unless clear context suggests otherwise
- Chinese: Use 您 for formal contexts, 你 for casual; prefer Taiwan terminology unless specified
- Punctuation: Use「」for quotes in JA/ZH Taiwan style; use《》for book titles in Chinese
- Idioms: When direct equivalent unclear, prioritize conveying meaning over preserving metaphor
Note: This is a core skill for trilingual translation work. For writing conventions specific to each language (document structure, essay formats, rhetorical patterns), see the document-writing skill. For technical terminology, see the engineering-terminology skill.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

