i18n

Standardize UI translations with ICU-like interpolation and locale-aware formatters.

Updated Dec 9, 2025
One-click install
npx skills add https://github.com/gzp79/shine-web-v2 --skill i18n-gzp79
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n
Source: https://github.com/gzp79/shine-web-v2/tree/main/.claude/skills/i18n
Command: npx skills add https://github.com/gzp79/shine-web-v2 --skill i18n-gzp79

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes translation workflows by providing ICU-like interpolation, a formatter system, and a centralized locale context to ensure consistent translations across UI.

Core Features & Use Cases

  • ICU-like interpolation with {key|formatter} syntax for consistent translations across locales.
  • Extendable formatter registry for dates, times, numbers, and custom formats.
  • Locale-aware translation loading with fallback, usable across components in multiple locales.

Quick Start

Initialize the locale context in your app and render translations with locale.t('section.key', { value }) for the current locale.

Frequently Asked Questions about i18n

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

FAQPage Schema
How do I handle UI text translation consistency with ICU-like interpolation across multiple locales?

UI text translation consistency is handled by standardizing ICU-like interpolation and formatters, applying locale-aware translations across components with a centralized context and fallback loading.

How do I format dates and numbers when translating UI text for different locales?

Formatting dates and numbers during UI translation is achieved through an extendable formatter registry, allowing custom formats for dates, times, numbers, and text using the {key|formatter} syntax.

What is the best way to load locale-aware translations with fallback for frontend components?

Loading locale-aware translations with fallback is managed by a centralized locale context, ensuring components retrieve the correct localized strings dynamically for locales like en or hu.

Can I use custom formatters with ICU-like interpolation in my frontend translation pipeline?

Custom formatters can be used with ICU-like interpolation through a modular formatter registry, extending the translation pipeline to support specific formatting needs for dates, numbers, and text.

Why do I need a centralized locale context for frontend translations?

A centralized locale context is needed to resolve translation consistency across UI components, standardizing interpolation and formatter application while supporting multiple locales with fallback mechanisms.