From Napkin
Guides adding a new language to a Next.js + next-intl app: translates message JSON, updates routing config, middleware, and UI toggle.
How this skill is triggered — by the user, by Claude, or both
Slash command
/napkin:next-intl-add-languageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This is a guide to add a new language to a Next.js project using next-intl for internationalization,
This is a guide to add a new language to a Next.js project using next-intl for internationalization,
./messages.src/components/language-toggle.tsx.src/i18n/routing.tssrc/middleware.tsWhen adding a new language:
en.json to the new language. The goal is to have all the JSON entries in the new language for a complete translation.routing.ts and middleware.ts.language-toggle.tsx.npx claudepluginhub ani1797/forge --plugin copilot-sdk2plugins reuse this skill
First indexed Jun 6, 2026
Add internationalization (i18n) to an existing T3/Next.js project using next-intl with sub-path routing. Uses `localePrefix: "as-needed"` so the default locale keeps its URLs unprefixed (preserving existing SEO and backlinks), and only non-default locales get a prefix.
Implements Next.js 16 internationalization with next-intl or a DIY dictionary approach. Covers locale routing, translations, formatting, SEO, and RTL support.
Adds internationalization to Next.js App Router projects using next-intl, with locale routing, translation files, hreflang sitemaps, and bulk translation across 14+ languages.