| name | transcreation |
| description | Transforms marketing content across languages and markets through
transcreation — adapting message, tone, and cultural references instead of
translating word for word — while honoring per-locale brand rules and a
do-not-translate glossary. Use when localizing content or when a locale is set.
Trigger with "transcreate", "localize", "adapt for a market", or "/localize".
|
| allowed-tools | Read, Write, Glob |
| argument-hint | --locales xx-XX,yy-YY [--brand <name>] [--back-translation] |
| version | 0.2.1 |
| author | localplugins <localplugins@proton.me> |
| license | MIT |
| compatibility | Designed for Claude Code |
| tags | ["localization","transcreation","marketing","content","internationalization"] |
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.
