translation-expertise▌
shino369/claude-code-personal-workspace · updated May 26, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
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.
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.
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.
How to use translation-expertise on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add translation-expertise
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches translation-expertise from GitHub repository shino369/claude-code-personal-workspace and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate translation-expertise. Access the skill through slash commands (e.g., /translation-expertise) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★52 reviews- ★★★★★Emma Chen· Dec 28, 2024
Useful defaults in translation-expertise — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Arjun Smith· Dec 12, 2024
Registry listing for translation-expertise matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Neel Verma· Dec 8, 2024
We added translation-expertise from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Fatima Anderson· Dec 4, 2024
Keeps context tight: translation-expertise is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Ama Ramirez· Nov 27, 2024
translation-expertise reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Neel Mehta· Nov 23, 2024
translation-expertise has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Rahul Santra· Nov 3, 2024
I recommend translation-expertise for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Ishan Martinez· Nov 3, 2024
I recommend translation-expertise for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Arjun Mehta· Nov 3, 2024
translation-expertise fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Pratham Ware· Oct 22, 2024
Useful defaults in translation-expertise — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 52