localization-strategy
When the user wants to plan or implement localization strategy for multilingual and global growth. Also use when the user mentions "localization," "multilingual," "i18n," "global expansion," "market entry," "localization strategy," "hreflang," "multi-language SEO," or "international SEO." For translation workflow, glossary, and style guide, use translation.
npx skills add kostja94/marketing-skills --skill localization --agent cursor
Same command for any agent — swap --agent for claude-code, codex, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 | |--------|---------|-------------| | **Subdirec
- Initial Assessment
- Localization vs. Translation
- Technical (i18n)
- URL Structure
- i18n SEO Principles
- Common Issues (Next.js + next-intl)
- SEO
- Keyword Research by Market
- Terminology & Translation
- Pricing Strategies
- i18n SEO Checklist (New Feature / New Locale)
- New feature with i18n
- New locale
- Multilingual Risks
What does the localization-strategy skill do?
When the user wants to plan or implement localization strategy for multilingual and global growth. Also use when the user mentions "localization," "multilingual," "i18n," "global expansion," "market entry," "localization strategy," "hreflang," "multi-language SEO," or "international SEO." For translation workflow, glossary, and style guide, use translation.
How do I install it?
Run `npx skills add kostja94/marketing-skills --skill localization --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From kostja94/marketing-skills, a repository with 848 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.