What problem does it solve?
This Skill helps you implement web application internationalization correctly across routing, message formats, SEO, and translation workflows without breaking rendering or translator pipelines.
Core Features & Use Cases
- Framework-aware i18n setup: Selects the right stack for Next.js (next-intl) vs Nuxt/Vue (vue-i18n via @nuxtjs/i18n) based on the project context.
- Correct locale routing + SEO wiring: Guides locale-prefixed strategies (always/as-needed/never), generates hreflang alternatives, sets canonical URLs, and supports per-locale sitemaps.
- Safe translation and runtime patterns: Covers ICU message structure, namespace organization, lazy-loading messages, and avoiding hydration mismatches when switching locales.
- Translation management workflow: Integrates with Crowdin, Lokalise, Phrase, and Tolgee with recommended git-first source control patterns.
- Troubleshooting guardrails: Prevents common pitfalls like incorrect setRequestLocale ordering, missing keys behavior, and Russian pluralization issues.
Quick Start
Use i18n to add Russian translations to my Next.js 16 App Router project with locale-prefixed routing, hreflang, lazy-loaded messages, and ICU plural rules.