i18n

Enforce i18n patterns across frontend apps to prevent hardcoded UI text.

4|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/rbaumier/skills --skill i18n-rbaumier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n
Source: https://github.com/rbaumier/skills/tree/main/i18n
Command: npx skills add https://github.com/rbaumier/skills --skill i18n-rbaumier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ZERO hardcoded user-visible text and inconsistent locale handling by providing standardized i18n patterns, translation structure, and SSR-safe initialization.

Core Features & Use Cases

  • Establishes a flat, domain-prefixed translation key framework (common., validation., errors.*) with TypeScript typings.
  • Defines locale detection order (user preference, URL, subdomain, Accept-Language, navigator.language) and CLDR-aware pluralization and formatting.
  • Integrates error translation for Zod form validation and API errors, route metadata, and SEO titles to ensure fully translated UIs.

Quick Start

Implement the i18n pattern by replacing plain strings with t() calls, wiring up the locale detector, and mapping errors to translation keys.

Frequently Asked Questions about i18n

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

FAQPage Schema
How do I prevent hardcoded UI text in React frontend apps?

To prevent hardcoded UI text in React frontend apps, replace plain strings with t() calls and enforce structured translation files. This establishes a flat, domain-prefixed key framework with TypeScript typings to ensure zero hardcoded user-visible text.

What is the best way to detect user locale for SSR-safe internationalization?

The best way to detect user locale for SSR-safe internationalization is to implement a prioritized detection order. This checks user preference, URL, subdomain, Accept-Language, and navigator.language sequentially to ensure robust locale handling.

How do I translate Zod form validation errors using translation keys?

To translate Zod form validation errors, map the error outputs to structured translation keys. This integrates error translation pipelines into your i18n setup, ensuring fully translated UIs for both form validations and API errors.

Does this i18n approach handle CLDR-aware pluralization and formatting?

Yes, this internationalization approach handles CLDR-aware pluralization and formatting. It applies standardized i18n patterns to enforce robust plural handling and date/number formatting across your frontend application.

How do I structure translation keys for a scalable frontend architecture?

Structure translation keys for scalable frontend architecture by using a flat, domain-prefixed framework. Organize keys into logical domains like common.*, validation.*, and errors.* to maintain consistency and enforce structured translation files.