i18n

Implement next-intl internationalization with locale routing and message formatting for Next.js projects.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/furrycolombia-sys/candyshop --skill i18n-furrycolombia-sys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: i18n
Source: https://github.com/furrycolombia-sys/candyshop/tree/main/.agents/skills/i18n
Command: npx skills add https://github.com/furrycolombia-sys/candyshop --skill i18n-furrycolombia-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Next.js projects often require consistent internationalization setup, which can be time-consuming and error-prone when done manually. This skill provides a Claude-aligned workflow to configure and manage translations using next-intl, ensuring consistent locale handling across apps.

Core Features & Use Cases

  • Claude-aligned workflow: Adapts the canonical Claude-driven SKILL.md into Codex for Next.js i18n setup.
  • Next.js internationalization: Streamlines creation of messages, locales, and routing for multi-language apps.
  • Use Case: A development team wants to add Spanish and French translations to a Next.js project with minimal boilerplate and a clear workflow.

Quick Start

Initialize the Next.js i18n setup by applying the Claude-aligned workflow to integrate next-intl into your project.

Frequently Asked Questions about i18n

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

FAQPage Schema
How do I set up internationalization in Next.js using next-intl?▼

To set up Next.js internationalization with next-intl, apply a Claude-aligned workflow that streamlines the creation of messages, locales, and routing for multi-language applications. This approach minimizes boilerplate and ensures consistent locale handling across your project.

What is the best way to add multiple locale translations to a Next.js project?▼

The best way to add multiple locale translations to a Next.js project is by applying a Claude-driven next-intl workflow. It configures locale routing and message formatting, providing a clear, consistent process for integrating languages like Spanish and French with minimal manual boilerplate.

Does this Next.js i18n workflow work in the Codex environment?▼

Yes, this Next.js i18n workflow works in the Codex environment by adapting the canonical Claude source from the SKILL.md file. It translates the Claude-aligned internationalization setup process to function within your current Codex project structure.

Can I use this skill to configure locale routing and message formatting?▼

Yes, you can use this skill to configure locale routing and message formatting. It applies a next-intl workflow specifically designed to handle these internationalization requirements, ensuring translations and locale switches operate correctly across your application.

Why does manual internationalization setup in Next.js cause errors?▼

Manual internationalization setup in Next.js causes errors because configuring locales, routing, and message files by hand is time-consuming and inconsistent. Using a Claude-aligned next-intl workflow eliminates this manual friction and ensures a standardized i18n configuration.