| name | blog-localize |
| description | 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 translation to swap brand examples, adapt CTAs, substitute legal references, localize statistic sources where possible, and adjust formality (Sie/du, tu/vous, formal/informal). Built-in profiles for DACH, Francophone, Hispanic, and Japanese markets, plus a custom-locale template. Makes content feel locally authored, not translated. Use when user says "localize blog", "blog localize", "cultural adaptation", "adapt for Germany", "adapt for France", "lokalisieren", "localiser", "adaptar".
|
| user-invokable | true |
| argument-hint | <file> --locale <locale-code> |
| license | MIT |
| compatibility | Standalone within claude-blog. Invoked by blog-multilingual. |
| metadata | {"author":"AgriciDaniel","version":"1.11.0","category":"blog"} |
Blog Localize, Cultural Deep-Adaptation
Takes a translated blog post and performs cultural adaptation so the result
feels like it was written for the target market, not translated into it.
This is the layer above blog-translate: it replaces examples, adjusts
tone, swaps references, and localizes the entire reading experience.
Adapted from claude-blog-multilingual by Chris Mueller (Pro Hub Challenge,
March 2026). Original: https://github.com/Chriss54/multilingual-int
Key References
../blog-translate/references/cultural-adaptation.md, the shared cultural
profiles file with substitution tables for DACH, Francophone, Hispanic,
Japanese, and a custom template. Do not duplicate this file.
When to Use
- Right after
blog-translate produces a base translation.
- When existing translated content reads like "translated from English".
- When targeting a specific market, not just a language.
- When content needs local statistics, examples, and brand references.
Workflow
Phase 1: Locale Understanding
- Parse the locale code with the shared multilingual locale rules used by
blog-translate, blog-multilingual, and blog-locale-audit: ISO 639-1
language in lowercase, optional ISO 15924 script in title case, optional
ISO 3166-1 Alpha-2 region in uppercase. Accept full codes (de-DE,
fr-CA, es-MX, pt-BR, zh-Hant) and unambiguous plain language codes
(de, fr). Require a region or explicit neutral mode for ambiguous
language-only targets such as es, pt, and zh.
- Load the cultural profile from
../blog-translate/references/cultural-adaptation.md.
- If the locale has a profile, use it.
- If not, follow the "Custom-locale template" section in that reference
to build a minimal profile inline.
- Read the translated post only after resolving it inside the project
root/current working directory. Reject symlinked paths, traversal outside
the root, files over 10 MB, and binary files. Then identify adaptation
targets.
Phase 2: Cultural Audit
Scan for elements that signal foreign origin:
