i18n
This skill equips your Next.js App Router project with complete i18n capabilities using next-intl v4. It walks you through setting up locale-based routing, extracting user-facing strings into translation files, and scaling translations across 14+ languages via parallel Codex agents—then verifies the results to catch missing keys or residual English content.
i18n adds full internationalization to Next.js using next-intl, supporting 14+ languages with SEO-friendly routing and bulk translation.
AI-generated summary based on this skill's SKILL.md
Install
OpenClaudia/openclaudia-skills/i18n · repository language: JavaScript
git clone https://github.com/OpenClaudia/openclaudia-skills
cp -r openclaudia-skills/skills/i18n ~/.claude/skills/i18nFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I add internationalization to Next.js?
i18n provides a complete setup for adding internationalization to Next.js using next-intl v4 with the App Router. The skill guides you through configuring locale-based routing, extracting user-facing strings into translation files, and deploying multi-language support across your application with built-in verification to catch missing translations.
What does i18n's next-intl implementation include?
i18n's next-intl implementation covers configuration with App Router, language switching setup, SEO-friendly locale routing with hreflang sitemaps, and RTL language support for locales like Arabic. It automates extraction of translatable content and enables bulk translation across 14+ languages using parallel Codex agents.
How can I set up multi-language Next.js project with i18n?
i18n walks you through setting up a multi-language Next.js project by configuring next-intl with locale prefixes, extracting strings into translation files, and scaling translations across 14+ languages. The skill includes verification tools to ensure no keys are missing and residual English content is removed from your localized app.
Does i18n support SEO-friendly locale routing?
Yes, i18n sets up SEO-friendly locale routing with hreflang sitemaps to signal language and regional variants to search engines. Combined with next-intl's App Router configuration, this ensures proper indexing and ranking for each language version of your Next.js website.
Can i18n translate content to multiple languages at scale?
i18n enables bulk translation of Next.js content across 14+ languages using parallel Codex agents for efficient processing. The skill extracts all user-facing strings, coordinates parallel translation workflows, and verifies results to catch missing keys or incomplete translations before deployment.
Does i18n support RTL languages like Arabic?
Yes, i18n enables RTL language support and locale-specific rendering for right-to-left languages like Arabic. The skill handles directional CSS adjustments and ensures your Next.js app displays correctly across both LTR and RTL locales with proper text alignment and component orientation.
SKILL.md
rendered from the published skill — quoted content, verbatim
Internationalize a Next.js Project
Add complete internationalization to a Next.js (App Router) project using next-intl v4. This skill handles routing, translation files, sitemap hreflang, and bulk translation across all locales.
Step 1: Assess the Project
- Check the Next.js version (
package.json) — must be 13+ with App Router - Check if i18n is already partially set up (look for
next-intl,next-i18next,[locale]routes) - Identify all pages/routes that need translation
- Identify all user-facing strings (hardcoded text in components)
- Ask the user which locales to support (default recommendation: en, es, fr, de, pt, ja, ar, zh, zh-tw, id, vi, ms, ru, hi)
Step 2: Install Dependencies
npm install next-intl
Step 3: Create i18n Configuration Files
Create 4 files
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
skills/i18n/SKILL.md