localization

Manage language detection, translation loading, and locale-specific formatting for applications.

1|1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/fabioc-aloha/AIRS_Data_Analysis --skill localization-fabioc-aloha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localization
Source: https://github.com/fabioc-aloha/AIRS_Data_Analysis/tree/main/.github/skills/localization
Command: npx skills add https://github.com/fabioc-aloha/AIRS_Data_Analysis --skill localization-fabioc-aloha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires next-intl, @formatjs/intl-localematcher, negotiator, intl-messageformat, tailwindcss-rtl, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the complexities of adapting software for diverse linguistic and cultural audiences, ensuring a seamless user experience across different regions.

Core Features & Use Cases

  • Internationalization (i18n): Architecting applications to support multiple languages and regions from the ground up.
  • Localization (l10n): Adapting content, UI, and functionality for specific locales, including language, date/time formats, and cultural nuances.
  • Use Case: A global SaaS product needs to support users in Brazil, Germany, and Japan. This Skill provides the framework for detecting user locale, loading appropriate translations, formatting dates and numbers correctly, and handling Right-to-Left (RTL) text for languages like Arabic.

Quick Start

Configure the Next.js application to support English, Spanish, and Portuguese (Brazil) locales using the provided middleware and request configuration.

Frequently Asked Questions about localization

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

FAQPage Schema
How do I implement internationalization in Next.js with RTL and locale detection?

Next.js internationalization is implemented by configuring middleware for language detection and loading translations. This Skill manages BCP 47 tags, ICU MessageFormat for plurals, and RTL text direction using tailwindcss-rtl.

What is the best way to handle locale-specific date and number formatting in a web app?

Locale-specific formatting is handled by loading locale-specific configurations and using intl-messageformat. This ensures dates, numbers, and cultural nuances are adapted correctly for diverse linguistic audiences.

How do I configure Next.js middleware to detect user language and load translations?

Next.js middleware detects user language by matching BCP 47 tags using @formatjs/intl-localematcher and negotiator. It then loads the appropriate translation files for the requested locale.

Does next-intl support Right-to-Left text direction and ICU MessageFormat for plurals?

Yes, next-intl supports Right-to-Left text direction and ICU MessageFormat for plurals. The Skill integrates tailwindcss-rtl for layout adjustments and intl-messageformat for complex plural rules.

Can I use Tailwind CSS to handle Right-to-Left layout for Arabic localization?

Yes, Tailwind CSS handles Right-to-Left layouts for Arabic localization using the tailwindcss-rtl dependency. It adjusts UI components and text direction seamlessly within the internationalization framework.

Why do I need BCP 47 language tags for application localization?

BCP 47 language tags are required for application localization to standardize locale identification across regions. They enable precise language detection and ensure the correct translations and formatting are loaded.