What problem does it solve? Setting up internationalization in Next.js 16 App Router projects involves many moving parts — locale routing, message files, locale switchers, hreflang tags, and static export constraints — and misconfigurations cause cryptic build failures like "Unable to find next-intl locale". This Skill provides a complete, ordered procedure to configure next-intl v4 correctly the first time. ## Core Features & Use Cases - Routing and Messages Setup: Creates defineRouting config, navigation helpers, request config, and per-locale JSON message files with identical key structure. - Static Export Support: Handles output: 'export' requirements including setRequestLocale, generateStaticParams, and the decision to skip src/proxy.ts in favor of CDN-level redirects. - SEO and Components: Builds locale switchers using @/i18n/navigation and generates hreflang tags from the routing config. - Use Case: You are building a bilingual (English/Italian) marketing site with Next.js 16 static export. Use this Skill to scaffold the full i18n layer, add a locale switcher, and verify all locale directories appear in the out/ build output. ## Quick Start Set up next-intl internationalization in my Next.js 16 App Router project with English and Italian locales, English as default, and static export enabled.