/region-config

name: region-config
description: "Configure a brand's regional settings — timezone, languages, currency, compliance regulations (GDPR, CCPA, APPI, LGPD, EU AI Act Article 50, and more), local platforms, business hours, holiday calendars, and data-residency rules — written to a persistent per-region config file plus a practical compliance checklist. Downstream commands like content-calendar, email-sequence, and performance-report inherit these settings automatically. Triggers on \"/digital-marketing-pro:region-config\", \"set up the Japan market\", \"what compliance rules apply in the EU\", \"configure timezone and currency for APAC\", \"add a new region for this brand\". Reads and updates the brand profile with the region list and compliance summary."

/digital-marketing-pro:region-config

Purpose

Configure regional and market-specific settings for a brand. Sets the timezone for scheduled content delivery, primary language for content generation, applicable compliance and privacy regulations, preferred local platforms, currency for budget and performance reporting, and business hours for communication scheduling. These settings propagate to all downstream commands so that campaigns, content, and reporting automatically respect regional requirements without manual adjustment each time.

This is a setup/configuration command. It writes persistent configuration files that other commands consume. Once a region is configured, commands like `/digital-marketing-pro:content-calendar`, `/digital-marketing-pro:email-sequence`, `/digital-marketing-pro:paid-advertising`, and `/digital-marketing-pro:performance-report` automatically inherit the region's timezone, language, compliance rules, and platform preferences.

Supports both single-market configurations (e.g., "Japan") and broad regional groupings (e.g., "APAC") depending on how granular the brand's market segmentation needs to be.

Input Required

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

• **Region name**: The market being configured — broad region (North America, Europe, APAC, LATAM, MENA) or specific market (Japan, Germany, Brazil, United Kingdom, Australia). Determines which compliance rules, platforms, and defaults apply
• **Timezone**: IANA timezone identifier — e.g., `America/New_York`, `Europe/London`, `Asia/Tokyo`. Used for content scheduling, reporting windows, and business hours calculations
• **Primary language**: The main language for content generation and audience communication in this region — e.g., English (US), English (UK), Japanese, German, Portuguese (BR)
• **Secondary languages** (optional): Additional languages used in the market for multilingual campaigns — e.g., French and German for Switzerland, English and Mandarin for Singapore
• **Currency**: ISO 4217 currency code for budget and performance reporting — e.g., USD, EUR, GBP, JPY, BRL. All financial metrics for this region render in this currency
• **Local platforms** (optional): Region-specific platforms to prioritize — e.g., LINE and Yahoo Japan for Japan, Kakao for South Korea, VK for Russia, WeChat for China, Mercado Libre for LATAM. Overrides global platform defaults for this market
• **Business hours** (optional): Operating hours for the region in local time — e.g., "09:00-18:00 Mon-Fri". Used to constrain SMS sends, chat responses, and notification timing. Defaults to standard business hours for the timezone if not specified
• **Holiday calendar** (optional): Region-specific public holidays and observances that affect scheduling — e.g., Golden Week (Japan), Diwali (India), Carnival (Brazil). If omitted, common holidays for the region are applied automatically
• **Data residency requirements** (optional): Whether data must remain within specific geographic boundaries — relevant for EU, China, Russia, and other jurisdictions with data localization laws
• **Industry-specific regulations** (optional): Sector-level compliance beyond general privacy laws — e.g., HIPAA for US healthcare, FCA for UK financial services, TGA for Australian therapeutic goods. Adds industry constraints on top of regional compliance rules
• **Set as default** (optional): Whether this region should become the brand's default region — used when no region is explicitly specified in other commands. Only one region can be the default at a time

Process

1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Apply brand voice, compliance rules for target markets (`skills/context-engine/compliance-rules.md`), and industry context. Also check for guidelines at `~/.claude-marketing/brands/{slug}/guidelines/_manifest.json` — if present, load restrictions. 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. **Check existing regional configs**: Look for existing region configuration files at `~/.claude-marketing/brands/{slug}/regions/`. If the specified region already exists, load it and show current settings — then ask whether to update or replace. If this is a new region, proceed with creation. List all currently configured regions for context. 3. **Apply compliance rules for the region**: Consult `skills/context-engine/compliance-rules.md` and map applicable regulations — GDPR for EU/EEA/UK markets, CCPA/CPRA for California, PDPA for Singapore and Southeast Asia, LGPD for Brazil, PIPA for South Korea, APPI for Japan, PIPEDA for Canada, and DPDPA (Digital Personal Data Protection Act) for India. For any EU/EEA market, also flag **EU AI Act Article 50** AI-content transparency obligations (applicable 2 August 2026): AI-generated marketing assets must carry machine-readable provenance (see `skills/c2pa-metadata/SKILL.md`) and, for deepfakes or public-interest text, a visible disclosure. Record all applicable regulations with their key requirements (cons