translation

Name: translation
Author: kostja94

753stars109forks

How to install translation?

kostja94/marketing-skills/translation

$npx -y skills add kostja94/marketing-skills --skill translation

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	# Content: Translation
2
3	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.
4
5	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.
6
7	## Scope
8
9	- Workflow: Brief → translate → review
10	- Terminology: Glossary creation and management
11	- Style guide: Voice, tone, formatting per language
12	- Human vs MT: When to use each; post-editing
13	- Quality: QA, consistency, SEO
14	- Market-specific: Terminology by region
15
16	## Initial Assessment
17
18	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.
19
20	Identify:
21	1. Content type: Product UI, marketing copy, blog, landing page, docs
22	2. Target language(s): Priority locales
23	3. Existing assets: Glossary, style guide, translation memory (TM)
24
25	---
26
27	## 1. Translation Workflow
28
29	### Brief → Translate → Review
30
31	\| Phase \| Purpose \| Output \|
32	\|-------\|---------\|--------\|
33	\| Brief \| Context, audience, tone, glossary reference, style guide \| Translator brief document \|
34	\| Translate \| First pass; use glossary + TM when available \| Draft translation \|
35	\| Review \| Native speaker review; consistency, brand voice, SEO \| Final translation \|
36
37	### Translator Brief
38
39	Include in every project:
40	- Context: What the content is for (landing page, product UI, blog)
41	- Audience: Target market, user persona
42	- Tone: Formal, casual, technical
43	- Glossary: Link or attach; mandatory terms
44	- Style guide: Reference or key rules
45	- Constraints: Character limits (UI), SEO keywords to include naturally
46
47	### Content-Type Workflow
48
49	\| Content Type \| Approach \| Notes \|
50	\|--------------\|----------\|-------\|
51	\| Product UI \| Glossary-critical; short strings; consistency \| Use TM; avoid machine translation \|
52	\| Marketing copy \| Brand voice; cultural adaptation \| Human translation; see terminology \|
53	\| Blog / Article \| SEO; natural keyword placement \| Re-research keywords in target language; don't translate keyword lists \|
54	\| Landing page \| Conversion-focused; CTA clarity \| Human; test localized CTAs \|
55	\| Technical docs \| Precision; glossary \| TM + glossary; consider MT + post-edit for high volume \|
56
57	---
58
59	## 2. Glossary & Terminology
60
61	### Glossary Purpose
62
63	- Consistency: Same term translated the same way across all content
64	- Brand: Product names, feature names, approved phrasing
65	- Compliance: Safety, legal, regulated terms
66	- Cost: Reduces rework; accelerates review
67
68	### Glossary Structure
69
70	\| Field \| Purpose \|
71	\|-------\|---------\|
72	\| Source term \| Original (e.g., English) \|
73	\| Target term \| Approved translation \|
74	\| Context \| Where it appears; usage note \|
75	\| Do not translate \| Brand names, product names (when applicable) \|
76
77	### Market-Specific Terminology
78
79	\| Term \| English \| Chinese \| Notes \|
80	\|------\|---------\|---------\|------\|
81	\| Generative AI \| Generative AI, GenAI \| AIGC (人工智能生成内容) \| Use "AIGC" for China; "Generative AI" for English \|
82	\| Influencer \| Influencer \| KOL (关键意见领袖) \| "KOL" common in Chinese marketing \|
83	\| User \| User \| 用户 \| Context-dependent \|
84	\| Dashboard \| Dashboard \| 控制台, 仪表盘 \| Choose one; document in glossary \|
85
86	Principle: Don't translate terminology lists; research how target market searches and speaks. See keyword-research for multi-language keyword research.
87
88	---
89
90	## 3. Style Guide (Translation)
91
92	### Elements to Define
93
94	\| Element \| Purpose \|
95	\|---------\|---------\|
96	\| Voice \| Brand personality; formal vs casual \|
97	\| Tone \| Varies by content type (support = helpful; marketing = persuasive) \|
98	\| Register \| Formal (您) vs informal (你) in languages that distinguish \|
99	\| Punctuation \| Quotation marks, spacing (e.g., no space before colon in French) \|
100	\| Formatting \| Dates, numbers, units; locale-specific \|
101	\| Forbidden \| Terms or phrases to avoid \|
102
103	### Per-Language Considerations
104
105	- Chinese: Simplified vs Traditional; measure word usage
106	- German: Formal (Sie) vs informal (du); compound nouns
107	- Japanese: Honorifics; keigo for formal contexts
108	- Arabic: RTL; formal vs dialect
109
110	---
111
112	## 4. Human vs Machine Translat

People who liked this also viewed

6 picks

Type

translation

753stars109forks

View on GitHub

How to install translation?

kostja94/marketing-skills/translation

$npx -y skills add kostja94/marketing-skills --skill translation

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Content: Translation
2
3	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.
4
5	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.
6
7	## Scope
8
9	- Workflow: Brief → translate → review
10	- Terminology: Glossary creation and management
11	- Style guide: Voice, tone, formatting per language
12	- Human vs MT: When to use each; post-editing
13	- Quality: QA, consistency, SEO
14	- Market-specific: Terminology by region
15
16	## Initial Assessment
17
18	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.
19
20	Identify:
21	1. Content type: Product UI, marketing copy, blog, landing page, docs
22	2. Target language(s): Priority locales
23	3. Existing assets: Glossary, style guide, translation memory (TM)
24
25	---
26
27	## 1. Translation Workflow
28
29	### Brief → Translate → Review
30
31	\| Phase \| Purpose \| Output \|
32	\|-------\|---------\|--------\|
33	\| Brief \| Context, audience, tone, glossary reference, style guide \| Translator brief document \|
34	\| Translate \| First pass; use glossary + TM when available \| Draft translation \|
35	\| Review \| Native speaker review; consistency, brand voice, SEO \| Final translation \|
36
37	### Translator Brief
38
39	Include in every project:
40	- Context: What the content is for (landing page, product UI, blog)
41	- Audience: Target market, user persona
42	- Tone: Formal, casual, technical
43	- Glossary: Link or attach; mandatory terms
44	- Style guide: Reference or key rules
45	- Constraints: Character limits (UI), SEO keywords to include naturally
46
47	### Content-Type Workflow
48
49	\| Content Type \| Approach \| Notes \|
50	\|--------------\|----------\|-------\|
51	\| Product UI \| Glossary-critical; short strings; consistency \| Use TM; avoid machine translation \|
52	\| Marketing copy \| Brand voice; cultural adaptation \| Human translation; see terminology \|
53	\| Blog / Article \| SEO; natural keyword placement \| Re-research keywords in target language; don't translate keyword lists \|
54	\| Landing page \| Conversion-focused; CTA clarity \| Human; test localized CTAs \|
55	\| Technical docs \| Precision; glossary \| TM + glossary; consider MT + post-edit for high volume \|
56
57	---
58
59	## 2. Glossary & Terminology
60
61	### Glossary Purpose
62
63	- Consistency: Same term translated the same way across all content
64	- Brand: Product names, feature names, approved phrasing
65	- Compliance: Safety, legal, regulated terms
66	- Cost: Reduces rework; accelerates review
67
68	### Glossary Structure
69
70	\| Field \| Purpose \|
71	\|-------\|---------\|
72	\| Source term \| Original (e.g., English) \|
73	\| Target term \| Approved translation \|
74	\| Context \| Where it appears; usage note \|
75	\| Do not translate \| Brand names, product names (when applicable) \|
76
77	### Market-Specific Terminology
78
79	\| Term \| English \| Chinese \| Notes \|
80	\|------\|---------\|---------\|------\|
81	\| Generative AI \| Generative AI, GenAI \| AIGC (人工智能生成内容) \| Use "AIGC" for China; "Generative AI" for English \|
82	\| Influencer \| Influencer \| KOL (关键意见领袖) \| "KOL" common in Chinese marketing \|
83	\| User \| User \| 用户 \| Context-dependent \|
84	\| Dashboard \| Dashboard \| 控制台, 仪表盘 \| Choose one; document in glossary \|
85
86	Principle: Don't translate terminology lists; research how target market searches and speaks. See keyword-research for multi-language keyword research.
87
88	---
89
90	## 3. Style Guide (Translation)
91
92	### Elements to Define
93
94	\| Element \| Purpose \|
95	\|---------\|---------\|
96	\| Voice \| Brand personality; formal vs casual \|
97	\| Tone \| Varies by content type (support = helpful; marketing = persuasive) \|
98	\| Register \| Formal (您) vs informal (你) in languages that distinguish \|
99	\| Punctuation \| Quotation marks, spacing (e.g., no space before colon in French) \|
100	\| Formatting \| Dates, numbers, units; locale-specific \|
101	\| Forbidden \| Terms or phrases to avoid \|
102
103	### Per-Language Considerations
104
105	- Chinese: Simplified vs Traditional; measure word usage
106	- German: Formal (Sie) vs informal (du); compound nouns
107	- Japanese: Honorifics; keigo for formal contexts
108	- Arabic: RTL; formal vs dialect
109
110	---
111
112	## 4. Human vs Machine Translat

People who liked this also viewed

6 picks

Type