i18n-frontend-implementer

Adds internationalization (i18n) infrastructure with translation plumbing, scalable key strategy, formatters for dates/numbers/currency, plural rules, and language switching. Use when implementing "internationalization", "translations", "multi-language support", or "i18n".

⭐2stars🔀0forks📁View on GitHub🕐Updated Dec 31, 2025⬇️3downloads

When & Why to Use This Skill

The i18n Frontend Implementer is a specialized Claude skill designed to automate the integration of internationalization (i18n) infrastructure within modern web applications. It streamlines the setup of translation plumbing using industry-standard libraries like next-intl and react-i18next, offering a scalable strategy for hierarchical translation keys, locale-aware formatting for dates and currencies, and seamless language-switching capabilities to enhance global user experience.

Use Cases

  • Scenario 1: Initializing a robust multi-language framework for a new Next.js or React project, including provider setup and directory structuring.
  • Scenario 2: Refactoring existing hardcoded text into a scalable, hierarchical translation key system to support future localization efforts.
  • Scenario 3: Implementing complex pluralization rules and localized data formatting (dates, numbers, currency) for international e-commerce platforms.
  • Scenario 4: Developing a user-friendly language switcher UI component that handles state management and supports Right-to-Left (RTL) language layouts.
namei18n-frontend-implementer
descriptionAdds internationalization (i18n) infrastructure with translation plumbing, scalable key strategy, formatters for dates/numbers/currency, plural rules, and language switching. Use when implementing "internationalization", "translations", "multi-language support", or "i18n".

i18n Frontend Implementer

Implement internationalization with next-intl, react-i18next, or similar libraries.

Core Setup

1. Install: npm install next-intl or react-i18next 2. Create dictionaries: locales/en.json, locales/es.json 3. Provider setup: Wrap app with IntlProvider 4. Translation keys: Hierarchical namespace structure 5. Formatters: Date, number, currency formatting 6. Language switcher: Dropdown or flags UI

Translation Structure

{
  "common": { "nav": { "home": "Home", "about": "About" } },
  "auth": { "login": "Sign In", "logout": "Sign Out" },
  "errors": { "required": "{field} is required" }
}

Usage Examples

const t = useTranslations('common');
<h1>{t('nav.home')}</h1>

// With plurals
t('items', { count: 5 }) // "5 items"

// With formatting
<p>{formatDate(date, { dateStyle: 'long' })}</p>

Best Practices

Use namespaces for organization, extract all text to translations, handle plurals properly, format dates/numbers per locale, provide language switcher, support RTL languages, lazy-load translations.