irismaker/localization-strategy
skills/localization/SKILL.md
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," "translate content," "hreflang," "multi-language SEO," or "international SEO."
$ install --global
skillsauthnpx skillsauth add irismaker/ai-agent-skills-hub localization-strategyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 23, 2026, 3:55 PM54.8s1 file scanned
SKILL.md
- name:
- localization-strategy
- description:
- 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," "translate content," "hreflang," "multi-language SEO," or "international SEO.
- version:
- 1.0.0
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 product marketing context first: If .claude/product-marketing-context.md or .cursor/product-marketing-context.md exists, read it for product, target markets, and brand.
Identify:
- Target markets: Priority languages/regions
- Product type: SaaS, AI tool, content
- 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 transfer less authority.
- Default locale: Root path for default (e.g.
/for English); prefix for others (/zh/,/de/). - IETF BCP 47: Use valid codes (
en,en-US,zh-CN,pt-BR). Same language, different country (e.g.de-DEvsde-AT) needs ≥20% content difference for Google to differentiate.
i18n SEO Principles
- No hardcoded strings: All user-facing text via translation dictionary.
- Symmetric alternates: Every locale page lists ALL other versions (including self-reference). ~75% of international sites have hreflang errors; missing reciprocal links is the most common.
- x-default: Always include for fallback when user language/location doesn't match any version.
- Canonical alignment: Canonical must match the same regional version hreflang refers to; misalignment causes Google to ignore hreflang.
- Full SEO coverage: Metadata, OpenGraph, JSON-LD (
inLanguage), and sitemap all locale-aware.
Common Issues (Next.js + next-intl)
| Issue | Solution |
|-------|----------|
| Route conflict | generateStaticParams(); validate locale |
| Auto redirect | localeDetection: false |
| Middleware | Apply only to prefixed paths (e.g. /zh) |
| URL duplication | Manual switcher; getLocalizedHref() |
SEO
- Hreflang on all language versions; self-reference + symmetric annotations.
- Language switcher: Use
<a>not<button>; links in initial HTML. - Canonical: Handle multi-domain if using local TLDs; align with hreflang.
- SPAs: Use sitemap-based hreflang as backup when HTML head is JS-rendered.
Keyword Research by Market
| Market | Tool | |--------|------| | Russia | Yandex Wordstat | | Korea | Naver DataLab | | Global | Google Keyword Planner, SEO tools |
Consider: Cultural expressions, search habits, competition, long-tail in small markets.
Terminology
- AIGC vs. GenAI: Use "AIGC" for China; "Generative AI" for English markets
- KOL vs. Influencer: "Influencer" in English; "KOL" in Chinese
- Avoid machine translation for product/marketing: Terminology, culture, SEO quality
Pricing Strategies
| Strategy | Use | |----------|-----| | True localization | Adjust price by purchasing power | | Cosmetic | Display currency only; same price | | Tools | Parity Deals, Chargebee |
i18n SEO Checklist (New Feature / New Locale)
New feature with i18n
- Add translation keys to all locale JSON files.
- Add
generateMetadata()with alternates (hreflang) per page. - Add JSON-LD with
inLanguageand translated fields. - Add page to sitemap with hreflang annotations.
- Set
langattribute on<html>; UTF-8 encoding.
New locale
- Add locale code to config; create
{code}.jsondictionary. - Register in sitemap locale list; regenerate.
- Add OpenGraph
localeandalternateLocale. - Ensure all alternates are symmetric (every page lists all versions).
Multilingual Risks
- Batch publishing: Too many translated pages at once can trigger de-indexing or thin-content penalties.
- Mitigation: Roll out slowly; ensure content is product/industry relevant; avoid Wikipedia-like breadth; monitor indexing in GSC.
Avoid
- IP-based redirects that override user preferences.
- Machine translation without localization for product/marketing.
- Missing reciprocal hreflang between language versions.
- Canonical tags that conflict with hreflang.
Output Format
- Market priority
- i18n approach
- Keyword strategy per market
- Pricing recommendation
- Technical checklist
- i18n SEO checklist (if applicable)
Related Skills
- pricing-strategy: Base price structure; localization-strategy covers pricing by market
- page-metadata: Hreflang implementation
- url-structure: URL hierarchy for i18n (subdirectories, subdomains)
- content-strategy: Multilingual content planning; avoid thin translations
- navigation-menu-generator: Language switcher SEO
- affiliate-marketing: Local affiliates for target markets
Related Skills
irismaker/video
tools
VerifiedTrustedCommunity
When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks. Also use when the user mentions 'video production,' 'AI video,' 'Remotion,' 'Hyperframes,' 'HeyGen,' 'Synthesia,' 'Veo,' 'Runway,' 'Kling,' 'Pika,' 'video generation,' 'AI avatar,' 'talking head video,' 'programmatic video,' 'video template,' 'explainer video,' 'product demo video,' 'video pipeline,' or 'make me a video.' Use this for video creation, generation, and production workflows. For video content strategy and what to post, see social-content. For paid video ad creative, see ad-creative.
1SKILL.mdUpdated May 1, 2026
irismaker/lead-magnets
tools
VerifiedTrustedCommunity
When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the user mentions "lead magnet," "gated content," "content upgrade," "downloadable," "ebook," "cheat sheet," "checklist," "template download," "opt-in," "freebie," "PDF download," "resource library," "content offer," "email capture content," "Notion template," "spreadsheet template," or "what should I give away for emails." Use this for planning what to create and how to distribute it. For interactive tools as lead magnets, see free-tool-strategy. For writing the actual content, see copywriting. For the email sequence after capture, see email-sequence.
1SKILL.mdUpdated May 1, 2026
irismaker/image
development
VerifiedTrustedCommunity
When the user wants to create, generate, edit, or optimize images for marketing — blog heroes, social graphics, product mockups, profile banners, listing visuals, or brand assets. Also use when the user mentions 'AI image generation,' 'generate an image,' 'create a graphic,' 'product mockup,' 'hero image,' 'social media graphic,' 'banner image,' 'cover photo,' 'profile banner,' 'listing screenshot,' 'Flux,' 'Midjourney,' 'DALL-E,' 'GPT Image,' 'Ideogram,' 'Gemini image,' 'Canva,' 'Figma,' 'image optimization,' 'compress images,' 'WebP,' or 'OG image.' Use this for general-purpose marketing image creation and optimization. For paid ad image creative and platform-specific ad specs, see ad-creative. For video production, see video.
1SKILL.mdUpdated May 1, 2026
irismaker/humanizer
testing
VerifiedTrustedCommunity
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases. Credits: Original skill by @blader - https://github.com/blader/humanizer
1SKILL.mdUpdated May 1, 2026