Translation Expertise

If you're working with English, Japanese, and Traditional Chinese, this gives you a structured three-step workflow (initial translation, proofreading, refinement) plus language-specific reference files for each. It covers the practical stuff like when to adapt idioms versus translating literally, how formality levels map across languages, and punctuation differences (full-width marks, different quotation styles). The QA checklist is thorough without being overbearing. What I like is that it doesn't pretend translation is just swapping words. It pushes you to think about tone, cultural context, and whether something will actually make sense to a native speaker. The separate reference files for particles, measure words, and keigo levels mean you're not hunting through documentation mid-project.

skills.sh installs: 673
GitHub stars: 4
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add shino369/claude-code-personal-workspace --skill translation-expertise --agent claude-code

Installs into .claude/skills of the current project.

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:

SKILL.md on GitHub