Transcreation
Overview
Transcreation adapts content into another language so it feels native, preserving intent, brand voice, and emotional impact rather than translating literally. The wording is reworked; the effect is kept.
Literal translation breaks marketing: idioms fall flat, humor is lost, and register goes wrong.
This skill loads the base brand profile and the target locale's overrides, reworks the copy for that market,
protects do-not-translate glossary terms, and re-checks compliance and channel limits for the new language.
It is instruction-driven and writes localized files, with no accounts, keys, or network access.
Prerequisites
- Source content to localize and one or more target locales in
xx-XX form (for example de-DE, ja-JP).
- The base brand profile plus any
content/brand/locales/<xx-XX>/ overrides. The skill uses Glob and Read to find and load them and Write to save each localized asset.
- The
style-guide.md glossary section (Product and Trademark Names) for do-not-translate terms, and the locale's compliance.md for market-specific rules.
Instructions
- Read the base brand files, then read any
locales/<xx-XX>/ overrides. Locale rules win for that market.
- Adapt, do not translate: rework idioms, humor, and references into locale equivalents, keeping the effect rather than the words.
- Set the register: choose the correct formality and honorifics for the persona and locale (Sie or du, keigo, tu or usted).
- Convert locale specifics: units, currency, date and number formats, names, and examples.
- Protect the glossary: never translate product names, trademarks, or taglines unless the brand supplies a sanctioned translation.
- Check the channel limit: text expands or contracts across languages, so re-fit each asset with the
channel-formats spec.
- Verify compliance against the locale's
compliance.md: disclaimers and prohibited terms can differ by country.
- Handle scripts: apply right-to-left rules for Arabic and Hebrew and correct spacing for CJK.
- When asked, emit a back-translation plus a short note on adaptation choices so a non-native approver can sign off.
Output
One localized file per asset per locale, mirroring the source filenames under a locale folder (for example de-DE/linkedin.md). Each asset is transcreated, glossary-safe, compliance-checked for that market, and re-fitted to its channel limit. When a back-translation is requested, each localized asset is paired with a literal back-translation and an adaptation note for approver sign-off.
Error Handling
| Condition |
Behavior |
| No locale override found |
Use the base brand rules; note that no market-specific overrides were applied |
| Glossary term has no sanctioned translation |
Keep the source term verbatim; never invent a localized name |
| Compliance rules differ by market |
Apply the locale's compliance.md; flag any claim that cannot cross the border |
| Text overflows the channel after adaptation |
Re-fit with channel-formats before writing the file |
| Idiom or joke has no equivalent |
Substitute a locally resonant alternative and record the choice in the adaptation note |
Examples
Example: localize into two markets
/localize post.md --locales de-DE,ja-JP
Loads each locale's overrides, transcreates the post for German and Japanese, protects glossary terms, and writes de-DE/ and ja-JP/ versions.
Example: request a back-translation
/localize offer.md --locales fr-FR --back-translation
Produces the French asset plus a literal back-translation and an adaptation note for sign-off.
Example: localized as part of multiply
/multiply brief.md --channels linkedin --locales es-ES
Drafts the LinkedIn asset, then transcreates it for Spanish and re-fits it to the channel limit.
Related skills
See also the companion skills brand-voice (per-locale voice and compliance) and channel-formats (re-fit expanded or contracted text to each channel).
Resources
- references/transcreation-guide.md — worked before/after transcreations, formality-by-locale guidance, glossary handling, unit, currency, and date conversion tables, right-to-left and CJK notes, and how to produce a back-translation.
- references/locale-checklist.md — a step-by-step per-locale checklist and the common failure modes (literal idioms, broken glossary terms, compliance carried across a border, overflowed channel limits).
1---2name: transcreation-23description: |4 Transforms marketing content across languages and markets through5 transcreation — adapting message, tone, and cultural references instead of6 translating word for word — while honoring per-locale brand rules and a7 do-not-translate glossary. Use when localizing content or when a locale is set.8 Trigger with "transcreate", "localize", "adapt for a market", or "/localize".9allowed-tools: Read, Write, Glob10argument-hint: '--locales xx-XX,yy-YY [--brand <name>] [--back-translation]'11version: "0.2.1"12author: localplugins <localplugins@proton.me>13license: MIT14compatibility: Designed for Claude Code15tags:16 - localization17 - transcreation18 - marketing19 - content20 - internationalization21metadata:22 source: https://skillmd.com/skills/jeremylongshore/transcreation-223---2425# Transcreation2627## Overview2829Transcreation adapts content into another language so it feels native, preserving intent, brand voice, and emotional impact rather than translating literally. The wording is reworked; the effect is kept.3031Literal translation breaks marketing: idioms fall flat, humor is lost, and register goes wrong.32This skill loads the base brand profile and the target locale's overrides, reworks the copy for that market,33protects do-not-translate glossary terms, and re-checks compliance and channel limits for the new language.34It is instruction-driven and writes localized files, with no accounts, keys, or network access.3536## Prerequisites3738- Source content to localize and one or more target locales in `xx-XX` form (for example `de-DE`, `ja-JP`).39- The base brand profile plus any `content/brand/locales/<xx-XX>/` overrides. The skill uses Glob and Read to find and load them and Write to save each localized asset.40- The `style-guide.md` glossary section (Product and Trademark Names) for do-not-translate terms, and the locale's `compliance.md` for market-specific rules.4142## Instructions43441. Read the base brand files, then read any `locales/<xx-XX>/` overrides. Locale rules win for that market.452. Adapt, do not translate: rework idioms, humor, and references into locale equivalents, keeping the effect rather than the words.463. Set the register: choose the correct formality and honorifics for the persona and locale (Sie or du, keigo, tu or usted).474. Convert locale specifics: units, currency, date and number formats, names, and examples.485. Protect the glossary: never translate product names, trademarks, or taglines unless the brand supplies a sanctioned translation.496. Check the channel limit: text expands or contracts across languages, so re-fit each asset with the `channel-formats` spec.507. Verify compliance against the locale's `compliance.md`: disclaimers and prohibited terms can differ by country.518. Handle scripts: apply right-to-left rules for Arabic and Hebrew and correct spacing for CJK.529. When asked, emit a back-translation plus a short note on adaptation choices so a non-native approver can sign off.5354## Output5556One localized file per asset per locale, mirroring the source filenames under a locale folder (for example `de-DE/linkedin.md`). Each asset is transcreated, glossary-safe, compliance-checked for that market, and re-fitted to its channel limit. When a back-translation is requested, each localized asset is paired with a literal back-translation and an adaptation note for approver sign-off.5758## Error Handling5960| Condition | Behavior |61|-----------|----------|62| No locale override found | Use the base brand rules; note that no market-specific overrides were applied |63| Glossary term has no sanctioned translation | Keep the source term verbatim; never invent a localized name |64| Compliance rules differ by market | Apply the locale's `compliance.md`; flag any claim that cannot cross the border |65| Text overflows the channel after adaptation | Re-fit with `channel-formats` before writing the file |66| Idiom or joke has no equivalent | Substitute a locally resonant alternative and record the choice in the adaptation note |6768## Examples6970**Example: localize into two markets**71> /localize post.md --locales de-DE,ja-JP7273Loads each locale's overrides, transcreates the post for German and Japanese, protects glossary terms, and writes `de-DE/` and `ja-JP/` versions.7475**Example: request a back-translation**76> /localize offer.md --locales fr-FR --back-translation7778Produces the French asset plus a literal back-translation and an adaptation note for sign-off.7980**Example: localized as part of multiply**81> /multiply brief.md --channels linkedin --locales es-ES8283Drafts the LinkedIn asset, then transcreates it for Spanish and re-fits it to the channel limit.8485## Related skills8687See also the companion skills `brand-voice` (per-locale voice and compliance) and `channel-formats` (re-fit expanded or contracted text to each channel).8889## Resources9091- [references/transcreation-guide.md](references/transcreation-guide.md) — worked before/after transcreations, formality-by-locale guidance, glossary handling, unit, currency, and date conversion tables, right-to-left and CJK notes, and how to produce a back-translation.92- [references/locale-checklist.md](references/locale-checklist.md) — a step-by-step per-locale checklist and the common failure modes (literal idioms, broken glossary terms, compliance carried across a border, overflowed channel limits).