localization-strategy

# Strategies: Localization Guides localization strategy for AI/SaaS products expanding into global markets. Covers i18n implementation, translation, pricing, and marketing adaptation--not just text translation. **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, target markets, and brand. Identify: 1. **Target markets**: Priority languages/regions 2. **Product type**: SaaS, AI tool, content 3. **Technical stack**: Next.js, React, etc. ## Localization vs. Translation Localization includes: - **Product**: Features, UI/UX, cultural adaptation - **Pricing**: True localization (adjust by market) vs. cosmetic (currency only) - **Marketing**: Channels, content, user personas - **Compliance**: GDPR, local regulations ## Technical (i18n) ### URL Structure Choose one; be consistent: | Option | Example | Pros / Cons | |--------|---------|-------------| | **Subdirectories** | `/en/`, `/de/`, `/zh/` | Recommended; maintains domain authority | | **Subdomains** | `de.example.com` | Separate hosting; less authority transfer | | **ccTLD** | `example.de` | Strongest geo signal; costly | - **Use subdirectories, not subdomains** for i18n; subdomains transf...