blog-localize

Name: blog-localize
Author: AgriciDaniel

1.3kinstalls251forks

How to install blog-localize?

agricidaniel/claude-blog/blog-localize

$npx -y skills add AgriciDaniel/claude-blog --skill blog-localize

Installs into the current project.

Summary

Cultural adaptation for translated content. Run AFTER blog-translate completes. Adjusts brand examples, CTAs, legal references, and formality for the target market (German, French, Japanese, Spanish, etc.). Deep cultural adaptation of translated blog posts. Goes beyond translatio

Files · 1

View on GitHub

SKILL.md

1	# Blog Localize, Cultural Deep-Adaptation
2
3	Takes a translated blog post and performs cultural adaptation so the result
4	feels like it was written for the target market, not translated into it.
5	This is the layer above `blog-translate`: it replaces examples, adjusts
6	tone, swaps references, and localizes the entire reading experience.
7
8	> Adapted from `claude-blog-multilingual` by Chris Mueller (Pro Hub Challenge,
9	> March 2026). Original: https://github.com/Chriss54/multilingual-int
10
11	## Key References
12
13	- `../blog-translate/references/cultural-adaptation.md`, the shared cultural
14	profiles file with substitution tables for DACH, Francophone, Hispanic,
15	Japanese, and a custom template. Do not duplicate this file.
16
17	## When to Use
18
19	- Right after `blog-translate` produces a base translation.
20	- When existing translated content reads like "translated from English".
21	- When targeting a specific market, not just a language.
22	- When content needs local statistics, examples, and brand references.
23
24	## Workflow
25
26	### Phase 1: Locale Understanding
27
28	1. Parse the locale code. Accept full codes (`de-DE`, `fr-CA`, `es-MX`,
29	`pt-BR`, `zh-TW`) or plain language codes (`de`, `fr`).
30	2. Load the cultural profile from
31	`../blog-translate/references/cultural-adaptation.md`.
32	- If the locale has a profile, use it.
33	- If not, follow the "Custom-locale template" section in that reference
34	to build a minimal profile inline.
35	3. Read the translated post and identify adaptation targets.
36
37	### Phase 2: Cultural Audit
38
39	Scan for elements that signal foreign origin:
40
41	\| Element \| What to look for \|
42	\|---------\|------------------\|
43	\| Brand examples \| US or UK brands with no relevance locally \|
44	\| Statistics sources \| US-only studies and surveys \|
45	\| CTAs \| American-style aggressive calls-to-action \|
46	\| Idioms \| Literally translated English expressions \|
47	\| Legal references \| Foreign laws (CCPA, FTC) where local law applies (DSGVO, RGPD) \|
48	\| Cultural references \| Foreign holidays, events, customs \|
49	\| Currency and pricing \| USD without conversion or context \|
50	\| Tone \| Too casual or too formal for the target market \|
51	\| Address form \| Inconsistent Sie/du, tu/vous, formal/informal \|
52
53	Output an audit report listing every target with severity (critical,
54	recommended, optional).
55
56	### Phase 3: Adaptation
57
58	#### 3a. Example Substitution
59
60	Swap foreign examples for local equivalents:
61
62	- Use WebSearch to find local case studies, brands, or scenarios.
63	- Replace inline, preserving the same argument and structure.
64	- If no local equivalent exists, keep the original but add local context
65	("In the German market, the equivalent dynamic is X").
66
67	#### 3b. Statistics Localization
68
69	- Search for equivalent local statistics (`[topic] statistik [country] 2025
70	2026`).
71	- If local data exists, swap the source and the figure together. Keep one
72	named source per claim.
73	- If not, keep the original stat but mark its geographic scope ("In the
74	US, ...").
75	- Never strip source attribution.
76
77	#### 3c. CTA Adaptation
78
79	Rewrite calls-to-action per the cultural profile:
80
81	- Adjust aggressiveness level (DACH and JA prefer informational, US prefers
82	imperative).
83	- Use culturally appropriate action verbs.
84	- Adapt urgency framing.
85
86	#### 3d. Tone Calibration
87
88	- Match formality per profile (DACH defaults to Sie for B2B, du for B2C
89	lifestyle; FR defaults to vous; JA shifts register sharply by audience).
90	- Ensure consistent formal or informal address throughout the entire
91	document.
92	- Match local content-style conventions.
93
94	#### 3e. Legal and Regulatory Context
95
96	- Replace references to foreign laws with local equivalents (CCPA becomes
97	DSGVO in DE, RGPD in FR, LGPD in BR).
98	- Add local compliance notes where they help the reader.
99	- Remove irrelevant foreign regulatory references.
100
101	#### 3f. Brand Example Swaps (Quick Map)
102
103	Profiles in `../blog-translate/references/cultural-adaptation.md` provide
104	substitution tables. Common examples:
105
106	\| Source (US) \| DACH \|

People who liked this also viewed

6 picks

Type

blog-localize

1.3kinstalls251forks

View on GitHub

How to install blog-localize?

agricidaniel/claude-blog/blog-localize

$npx -y skills add AgriciDaniel/claude-blog --skill blog-localize

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Blog Localize, Cultural Deep-Adaptation
2
3	Takes a translated blog post and performs cultural adaptation so the result
4	feels like it was written for the target market, not translated into it.
5	This is the layer above `blog-translate`: it replaces examples, adjusts
6	tone, swaps references, and localizes the entire reading experience.
7
8	> Adapted from `claude-blog-multilingual` by Chris Mueller (Pro Hub Challenge,
9	> March 2026). Original: https://github.com/Chriss54/multilingual-int
10
11	## Key References
12
13	- `../blog-translate/references/cultural-adaptation.md`, the shared cultural
14	profiles file with substitution tables for DACH, Francophone, Hispanic,
15	Japanese, and a custom template. Do not duplicate this file.
16
17	## When to Use
18
19	- Right after `blog-translate` produces a base translation.
20	- When existing translated content reads like "translated from English".
21	- When targeting a specific market, not just a language.
22	- When content needs local statistics, examples, and brand references.
23
24	## Workflow
25
26	### Phase 1: Locale Understanding
27
28	1. Parse the locale code. Accept full codes (`de-DE`, `fr-CA`, `es-MX`,
29	`pt-BR`, `zh-TW`) or plain language codes (`de`, `fr`).
30	2. Load the cultural profile from
31	`../blog-translate/references/cultural-adaptation.md`.
32	- If the locale has a profile, use it.
33	- If not, follow the "Custom-locale template" section in that reference
34	to build a minimal profile inline.
35	3. Read the translated post and identify adaptation targets.
36
37	### Phase 2: Cultural Audit
38
39	Scan for elements that signal foreign origin:
40
41	\| Element \| What to look for \|
42	\|---------\|------------------\|
43	\| Brand examples \| US or UK brands with no relevance locally \|
44	\| Statistics sources \| US-only studies and surveys \|
45	\| CTAs \| American-style aggressive calls-to-action \|
46	\| Idioms \| Literally translated English expressions \|
47	\| Legal references \| Foreign laws (CCPA, FTC) where local law applies (DSGVO, RGPD) \|
48	\| Cultural references \| Foreign holidays, events, customs \|
49	\| Currency and pricing \| USD without conversion or context \|
50	\| Tone \| Too casual or too formal for the target market \|
51	\| Address form \| Inconsistent Sie/du, tu/vous, formal/informal \|
52
53	Output an audit report listing every target with severity (critical,
54	recommended, optional).
55
56	### Phase 3: Adaptation
57
58	#### 3a. Example Substitution
59
60	Swap foreign examples for local equivalents:
61
62	- Use WebSearch to find local case studies, brands, or scenarios.
63	- Replace inline, preserving the same argument and structure.
64	- If no local equivalent exists, keep the original but add local context
65	("In the German market, the equivalent dynamic is X").
66
67	#### 3b. Statistics Localization
68
69	- Search for equivalent local statistics (`[topic] statistik [country] 2025
70	2026`).
71	- If local data exists, swap the source and the figure together. Keep one
72	named source per claim.
73	- If not, keep the original stat but mark its geographic scope ("In the
74	US, ...").
75	- Never strip source attribution.
76
77	#### 3c. CTA Adaptation
78
79	Rewrite calls-to-action per the cultural profile:
80
81	- Adjust aggressiveness level (DACH and JA prefer informational, US prefers
82	imperative).
83	- Use culturally appropriate action verbs.
84	- Adapt urgency framing.
85
86	#### 3d. Tone Calibration
87
88	- Match formality per profile (DACH defaults to Sie for B2B, du for B2C
89	lifestyle; FR defaults to vous; JA shifts register sharply by audience).
90	- Ensure consistent formal or informal address throughout the entire
91	document.
92	- Match local content-style conventions.
93
94	#### 3e. Legal and Regulatory Context
95
96	- Replace references to foreign laws with local equivalents (CCPA becomes
97	DSGVO in DE, RGPD in FR, LGPD in BR).
98	- Add local compliance notes where they help the reader.
99	- Remove irrelevant foreign regulatory references.
100
101	#### 3f. Brand Example Swaps (Quick Map)
102
103	Profiles in `../blog-translate/references/cultural-adaptation.md` provide
104	substitution tables. Common examples:
105
106	\| Source (US) \| DACH \|

People who liked this also viewed

6 picks

Type