localize-campaign

name	localize-campaign
description	Localize an entire campaign — emails, ads, social posts, landing pages, video scripts — for multiple markets, producing a deployment-ready per-market package: translations, transcreation options for emotional copy, Hofstede-based cultural adaptation notes, market-specific compliance additions, localized SEO and hreflang specs, RTL and locale formatting, quality scores, and a cross-market consistency report. Triggers on "/digital-marketing-pro:localize-campaign", "localize this campaign for Germany and Japan", "adapt these assets for new markets", "take the Q3 campaign multilingual", "prepare our launch for hi-IN and ar-SA". Prepares and scores assets but publishes nothing — each package ships with a deployment checklist. Reads the brand profile's language config and do-not-translate terms; for a single piece use /digital-marketing-pro:translate-content.
argument-hint	[target-markets]

/digital-marketing-pro:localize-campaign

Purpose

Full campaign localization across multiple target markets. This command takes all campaign assets — emails, ads, social posts, landing pages, video scripts, push notifications — and adapts them for each target market. It goes far beyond translation: cultural references are adjusted, compliance elements are modified per region, SEO is localized, creative recommendations are adapted, and assets are prepared for multilingual publishing.

This is the comprehensive localization workflow for market expansion. Where /digital-marketing-pro:translate-content handles a single piece of content, /digital-marketing-pro:localize-campaign orchestrates the localization of an entire campaign across multiple markets simultaneously. It coordinates translation service routing per language, transcreation for emotional content, market-specific compliance additions, cultural adaptation based on Hofstede cultural dimensions, localized SEO, RTL formatting for applicable languages, and produces a deployment-ready package per market with quality scores and publishing checklists.

Input Required

The user must provide (or will be prompted for):

• Campaign assets: Content for localization, provided as:
  • File paths per asset type (e.g., "emails: /campaign/email-welcome.html, /campaign/email-follow-up.html; ads: /campaign/fb-ad.txt, /campaign/google-ad.txt; social: /campaign/ig-post.txt")
  • A campaign directory (e.g., "/campaign-q1/") — all files will be categorized by type based on naming conventions or metadata
  • Inline content blocks with asset type labels
• Target markets: One or more market codes in language-region format (e.g., hi-IN, de-DE, ja-JP, fr-FR, ar-SA, pt-BR, es-MX). Each code specifies both the language and the cultural/regulatory context
• Campaign brief or strategy document: Optional — provides campaign objectives, messaging hierarchy, key themes, and audience segments. Used to inform transcreation decisions and ensure localized versions maintain strategic alignment
• Market-specific compliance requirements: Optional — additional regulatory, legal, or industry requirements per market beyond what is already in the brand profile (e.g., "Germany requires Impressum link", "India requires MRP display", "Saudi Arabia prohibits alcohol imagery references")
• Budget allocation per market: Optional — if provided, influences prioritization (higher-budget markets get full transcreation and deeper cultural adaptation; lower-budget markets get quality translation with standard adaptation)
• Priority markets: Optional — markets to process first and with the most thorough adaptation. Other markets receive standard localization
• Asset priority: Optional — which asset types are most important (e.g., "landing pages are highest priority, social posts are secondary"). Affects depth of review and transcreation effort

Process

1. Load brand context: Read ~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Extract full language configuration — do_not_translate terms, translation_preferences, locale_formatting rules per market, approved markets list. Load compliance rules for every target market from skills/context-engine/compliance-rules.md. Check for guidelines at ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json — if present, load voice-and-tone rules, messaging hierarchy, channel style guides, and any market-specific brand guidelines. Check for custom templates at ~/.claude-marketing/brands/{slug}/templates/ — localized templates may already exist for some markets. Check for agency SOPs at ~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults.
2. Inventory all campaign assets: Enumerate every asset from the provided sources. Categorize each by type (email, ad, social post, landing page, video script, push notification, SMS, blog post). For each asset, analyze the content to classify it as:
   • Factual/informational: Product descriptions, specifications, terms, pricing — suitable for direct translation
   • Emotional/creative: Headlines, CTAs, slogans, hero copy, storytelling — requires transcreation
   • Compliance-sensitive: Disclaimers, consent language, legal text, privacy notices — requires market-specific adaptation
   • SEO-dependent: Landing pages, blog posts, meta content — requires localized keyword research Report the full inventory to the user: total asset count, breakdown by type, breakdown by content classification, and estimated processing scope per market.
3. For each target market, execute the following localization pipeline: a. Route translation service: Run python "${CLAUDE_PLUGIN_ROOT}/scripts/language-router.py" --action route --source "{source_lang}" --target "{market_lang}" to select the optimal translation service for this language pair. Log the selected service. b. Translate factual content: Process all factual/informational assets through whatever the route action resolved — the brand's preferred server, a connected translation MCP, or (when basis: unresolved) the harness's own multilingual capability per translate-content's execution rules. Pass or enforce do-not-translate terms, glossary entries, formality settings, and formatting preservation flags. Score each translation via . c. : For all emotional/creative assets, apply the transcreation methodology from . Produce 2-3 creative adaptation options per piece, each with:

Output

A comprehensive campaign localization package containing:

• Per-market asset package: For each target market:
  • All localized content organized by asset type (email, ad, social, landing page, etc.)
  • Translation quality score per asset with dimension breakdown
  • Content quality score per asset (eval-runner assessment)
  • Brand voice score for key assets
• Transcreation options: For all emotional/creative content across all markets — 2-3 options per piece with back-translations, intent-preservation scores, cultural fit notes, and recommended option marked
• Cultural adaptation notes: Per-market summary of what was adapted and why — social proof style, urgency tactics, trust signals, humor adjustments, imagery recommendations, with Hofstede dimension references
• Compliance additions per market: Every disclaimer, consent statement, regulatory notice, and required disclosure added for each market, with regulatory references (GDPR Article X, DPDPA Section Y, etc.)
• Localized SEO recommendations: Per-market keyword suggestions, hreflang tag specifications, localized meta titles and descriptions, URL slug recommendations
• RTL and formatting notes: For applicable markets — RTL layout flags, date/number/currency format specifications, measurement unit conversions, address and phone format conventions
• Cross-market consistency report: Verification that brand messaging, campaign themes, and value propositions are coherent across all markets, with flags for significant divergences
• Quality scoreboard: Matrix of all markets (rows) by all assets (columns) with translation quality scores, content quality scores, and overall grades — provides an at-a-glance view of campaign localization health
• Deployment checklist per market: Market-specific steps for publishing — platform settings, language targeting, geo-targeting, compliance approvals needed, QA review points, go-live sequence
• Campaign localization health score: Single aggregate score reflecting overall localization quality, consistency, and completeness across all markets
• Recommendations: Priority items for human review (low-scoring assets, culturally sensitive transcreation decisions, compliance items requiring legal sign-off), process improvements for future localization runs, and terms to add to the brand glossary

Agents Used

• localization-specialist -- Manages the end-to-end localization pipeline including translation service routing, transcreation execution, cultural adaptation using Hofstede dimensions, compliance localization, quality scoring, cross-market consistency verification, and per-market package assembly
• content-creator -- Generates transcreation options for emotional and creative content, produces culturally adapted headlines and CTAs, creates localized meta descriptions and SEO copy, and ensures marketing effectiveness is preserved across languages
• execution-coordinator -- Coordinates the multi-market publishing workflow, manages deployment checklists, sequences go-live across markets and channels, tracks approval status per market, and ensures all compliance sign-offs are obtained before publishing