content-localizerlisted

# Content Localizer Expand your content to new language markets — culturally adapted, not just translated. ## When to Activate - User says `/translate {file} en` or `/translate {file} ja` - User says `/localize {file} {target_lang}` - User asks "translate this to English" - User asks "localize this overseas article for Japanese readers" ## Prerequisites - `~/.content-autopilot/profile.json` must exist - Source content file to localize ## Commands ### `/translate {file_path} en` — Localize Japanese content for English market ### `/translate {file_path} ja` — Localize English content for Japanese market ### `/translate` — Interactive: select source and target ## Localization vs Translation | Aspect | Translation | Localization (what we do) | |--------|------------|--------------------------| | Text | Word-for-word conversion | Meaning-preserving adaptation | | Examples | Keep original references | Replace with locally relevant ones | | Data | Same statistics | Add local market data | | Humor | Direct translation (often fails) | Culturally appropriate equivalent | | CTA | Same call to action | Platform-appropriate CTA | | Length | ~Same | Adjusted for platform norms | | SEO | Same keywords translated | Locally researched keywords | ## Workflow ### Step 1: Load Source Content Read the file and identify: - Source language (auto-detect from content) - Content type (article, thread, caption) - Key concepts, data, examples, references - Cultural references that need adapt