add-i18n

Configures internationalization for Next.js App Router projects using the next-intl library with SEO-friendly locale routing.

34|6|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/flavien-ia/hypervibe-harness --skill add-i18n-flavien-ia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-i18n
Source: https://github.com/flavien-ia/hypervibe-harness/tree/main/skills/add-i18n
Command: npx skills add https://github.com/flavien-ia/hypervibe-harness --skill add-i18n-flavien-ia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires next-intl, and includes scripts (resource) components.

What problem does it solve?

This skill removes the complexity of manual internationalization setup, ensuring your application can serve a global audience without breaking existing SEO or routing logic.

Core Features & Use Cases

  • Automated Scaffolding: Automatically configures next-intl, middleware, and locale-aware routing for Next.js App Router projects.
  • SEO Preservation: Implements localePrefix as-needed to ensure your default language URLs remain clean and indexed correctly.
  • Use Case: You have a French-only T3 project and need to expand to English and Spanish; this skill handles the directory restructuring, message file generation, and hreflang implementation in one go.

Quick Start

Use the add-i18n skill to configure internationalization for my project with English and Spanish support.

Frequently Asked Questions about add-i18n

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add internationalization to a Next.js App Router project?

Adding internationalization to a Next.js App Router project is handled by configuring next-intl, restructuring directories, and scaffolding message files to support multiple languages automatically.

Can I set up multilingual routing in Next.js without breaking my existing SEO?

Setting up multilingual routing preserves SEO by implementing an as-needed locale prefix, keeping default language URLs clean and correctly indexed while generating per-page canonical metadata.

What is the best way to automate next-intl scaffolding for a T3 application?

Automating next-intl scaffolding for a T3 application is done by running a script that generates middleware, restructures directories, and implements locale-aware routing simultaneously.

Do I need pnpm to configure next-intl sub-path routing?

You need pnpm in a Node.js environment to configure next-intl sub-path routing, because the automated directory restructuring and message scaffolding processes depend on this specific environment.

Does this internationalization approach support hreflang implementation automatically?

This internationalization approach supports hreflang implementation automatically by generating per-page canonical metadata and SEO-friendly locale prefixes during the directory restructuring process.