plugins/nextjs-expert/skills/nextjs-i18n/SKILL.md
Next.js 16 internationalization with next-intl or DIY. Use when implementing i18n, translations, localization, multilingual, language switch, locale routing, or formatters.
npx skillsauth add fusengine/agents nextjs-i18nInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Complete i18n solution with next-intl or DIY dictionary approach.
Before ANY implementation, use TeamCreate to spawn 3 agents:
After implementation, run fuse-ai-pilot:sniper for validation.
[locale] dynamic segment| Feature | Benefit | |---------|---------| | App Router native | Full Server Components support | | Type-safe messages | TypeScript autocompletion for keys | | ICU MessageFormat | Pluralization, gender, select expressions | | Async message loading | Load translations on-demand per locale | | proxy.ts compatible | Works with Next.js 16 proxy pattern | | Rich formatting | Dates, numbers, lists, relative time |
Full-featured library with routing, formatting, and type safety. Best for production applications needing comprehensive i18n support.
Lightweight approach using dynamic imports for simple translation needs. Good for projects wanting minimal dependencies.
All i18n code organized in modules/cores/i18n/:
src/modules/cores/i18n/src/config/routing.ts - Locale routing configsrc/modules/cores/i18n/messages/en.json - English translationssrc/modules/cores/i18n/messages/fr.json - French translationsproxy.ts - Locale detection and redirect logicAll routes prefixed with [locale] dynamic segment:
/en/about → English about page/fr/about → French about page/ → Redirects to default localeUse localized navigation from next-intl for automatic locale handling:
| Need | Reference | |------|-----------| | Initial setup | installation.md, routing-setup.md | | Route config | routing-config.md, middleware-proxy.md | | Translations | translations.md, messages-validation.md | | Formatting | formatting.md | | Components | server-components.md, client-components.md | | Navigation | navigation.md | | TypeScript | typescript.md | | SEO | seo.md | | Testing | testing.md | | DIY approach | diy-dictionaries.md, diy-locale-detection.md |
{count, plural, one {# item} other {# items}}{gender, select, male {He} female {She} other {They}}dir attribute for right-to-left languagesLocalized error and loading states require specific handling:
[locale]/error.tsx - Localized error boundary[locale]/not-found.tsx - Localized 404 pageglobal-error.tsx - Root error fallbackSee error-files.md for complete patterns.
development
Use when optimizing entity-based / semantic SEO 2026. Covers entity maps, Google Knowledge Graph resolution, salience scoring, passage-level ranking, about/sameAs/knowsAbout schema, Cloud Natural Language API validation.
development
Use when running SEO, GEO, schema, Core Web Vitals, sitemap, hreflang, E-E-A-T, AI Overviews, technical SEO, or structured data tasks. Covers full-site audits, single-page analysis, schema markup, content quality, AI search optimization, local SEO, sitemap/robots, internal linking, semantic clustering, and search experience.
development
Use when optimizing search experience (SXO). Covers intent matching, user personas, user stories, page-type analysis, dwell time, scroll depth, pogo-sticking prevention.
development
Use when optimizing local SEO. Covers Google Business Profile, NAP consistency, citations, reviews acquisition, Local Pack ranking, location pages, LocalBusiness schema.