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.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
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:
| 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 |
Include in every project:
| 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 |
| 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) |
| 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.
| 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 |
| 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 |
| Scenario | Condition |
|---|---|
| High-volume, low-stakes | Internal docs, user-generated content |
| Draft / triage | MT + human post-edit (MTPE) |
| Real-time | Chat, support; with disclaimer |
| 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).
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
日本語の概要は準備中です。原文の説明を表示しています。