| 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 antigravity-blog. Invoked by blog-multilingual. |
| metadata | {"author":"dotusmanali","version":"2.0.0","category":"blog"} |
| id | blog-localize |
| domain | content |
| invoked_by | ["blog-translator"] |
| depends_on | [] |
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 antigravity-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. Accept full codes (
de-DE, fr-CA, es-MX,
pt-BR, zh-TW) or plain language codes (de, fr).
- 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 and identify adaptation targets.
Phase 2: Cultural Audit
Scan for elements that signal foreign origin:
| Element | What to look for |
|---|
| Brand examples | US or UK brands with no relevance locally |
| Statistics sources | US-only studies and surveys |
| CTAs | American-style aggressive calls-to-action |
| Idioms | Literally translated English expressions |
| Legal references | Foreign laws (CCPA, FTC) where local law applies (DSGVO, RGPD) |
