What problem does it solve? Retrofitting language routing into a finished landing page is a classic budget trap. This Skill locks the i18n decisions before design begins, covering URL structure, locale detection, hreflang, and per-locale content strategy for bilingual EN/PL marketing sites. ## Core Features & Use Cases - Decision Framework: Locks URL structure (default locale at /, secondary at /pl/), first-visit-only detection via Accept-Language, and a persistent visible language toggle. - SEO Requirements: Specifies hreflang pairs (en, pl-PL, x-default) and indexability rules so both locale versions rank without JS-only swaps. - Per-Locale Proof Strategy: Directs market-specific evidence per locale (PLN pricing and EU data residency for PL; GitHub stars and benchmarks for EN) rather than literal translation. - Use Case: When building a bilingual landing page, use this Skill to hand the implementer concrete build requirements — framework-native i18n routing, namespaced key files, locale-aware formatting, and acceptance checks. ## Quick Start Use the geo i18n strategy skill to define the URL structure, redirect rules, and hreflang setup for my bilingual EN/PL marketing site.