skills.rest
Vincri126
Vincri126COMMUNITY
Explore all skills by this author →
GitHub

i18n-localization

Automate translation planning, ICU formatting, and QA gating for React/Next.js apps.

Updated Aug 27, 2026
Search Tags:#react#localization#nextjs#i18n#rtl#icu#qa-gates
One-click install
npx skills add https://github.com/Vincri126/MCO-Template --skill i18n-localization-vincri126
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: i18n-localization
Source: https://github.com/Vincri126/MCO-Template/tree/main/.orchestrator/skills/i18n-localization
Command: npx skills add https://github.com/Vincri126/MCO-Template --skill i18n-localization-vincri126

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, numfmt, and includes scripts (resource) and references (resource) components.

What problem does it solve?

It prevents front-end teams from shipping brittle translations and inconsistent locale behavior by providing a comprehensive architecture, workflow, and QA guardrail for React/Next.js projects that need accurate multilingual content, RTL support, and SEO-friendly localization.

Core Features & Use Cases

  • Architectural Playbook for locale detection, fallback chains, Next.js App Router integration, routing strategies, and SEO hreflang metadata so every new page echoes its translations consistently.
  • Translation Workflow & ICU Guidance covering message extraction, ICU MessageFormat patterns, glossary maintenance, TM integration, and translator handoffs documented in the references for quick onboarding.
  • QA Gate Automation that runs the provided shell script to validate translation JSON files, detect missing keys, enforce ICU syntax, check RTL dir attributes, and monitor bundle sizes before global releases, ensuring a React/Next.js multilingual launch does not regress.

Quick Start

Ask the skill to produce a React/Next.js i18n implementation checklist covering locale detection, ICU formatting, RTL layouts, translation QA gates, and SEO hreflang updates.

Frequently Asked Questions about i18n-localization

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

FAQPage Schema
How do I set up React i18n with ICU MessageFormat and RTL support?▼

Setting up React i18n involves configuring locale detection, fallback chains, and JSON message catalogs with ICU MessageFormat. You must also enforce RTL dir attributes and implement SEO hreflang metadata for consistent multilingual rendering in Next.js.

What is the best way to automate translation QA gates for Next.js localization?▼

Automating translation QA gates involves running a shell script to validate JSON message catalogs, detect missing translation keys, enforce ICU MessageFormat syntax, check RTL dir attributes, and monitor locale bundle sizes to prevent multilingual regressions.

Does this i18n approach work with Next.js App Router for SEO hreflang metadata?▼

Yes, the Next.js App Router supports this i18n approach through integrated locale routing strategies and SEO-aware hreflang metadata generation. It ensures every new page echoes its translations consistently for accurate search engine indexing.

How do I handle ICU MessageFormat patterns and translator workflows in a multilingual web app?▼

Handling ICU MessageFormat patterns requires message extraction, glossary maintenance, and translation memory integration. You must document translator handoffs in references to ensure smooth onboarding and consistent multilingual content delivery.

Why do I need jq and numfmt for translation QA gating?▼

You need jq and numfmt for translation QA gating because the provided shell script depends on them to parse JSON message catalogs and format numerical data. These dependencies enable accurate ICU syntax validation and locale bundle size monitoring.

What are the limitations of relying on JSON message catalogs for React localization?▼

Relying on JSON message catalogs for React localization requires strict QA gates to prevent missing keys and brittle translations. Without enforcing ICU syntax validation and RTL dir attribute checks, your multilingual web app may render inconsistently.

Related Skills

Explore More Software Engineering Skills→
Aqsagull99Aqsagull99

nextjs-skill

Build Next.js 16+ apps with App Router, server components, and API routes.

Community
Intermediate
oakossoakoss
14

localization-engineer

Implement framework-agnostic i18n and l10n patterns for multilingual applications.

Official
Advanced
kaptinlinkaptinlin
23

go-i18n-localizing

Localize Go applications with ICU MessageFormat and JSON translation bundles.

Community
Intermediate
jamieadams-nerdjamieadams-nerd

i18n-l10n-rules

Enforce i18n/l10n guidelines for locale detection and gettext wiring.

Community
Advanced