skills.rest
junevm
junevmCOMMUNITY
Explore all skills by this author →
GitHub

localization-engineer

Implement framework-agnostic internationalization with ICU messages, CLDR plurals, and RTL handling.

Updated Aug 23, 2026
Search Tags:#localization#i18n#rtl#hreflang#icu#cldr pluralization#locale detection
One-click install
npx skills add https://github.com/junevm/avtoolz --skill localization-engineer-junevm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: localization-engineer
Source: https://github.com/junevm/avtoolz/tree/main/.agents/skills/localization-engineer
Command: npx skills add https://github.com/junevm/avtoolz --skill localization-engineer-junevm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams implement consistent internationalization and localization so multilingual apps render correctly across plural rules, RTL layouts, formatting, locale detection, and SEO requirements.

Core Features & Use Cases

  • ICU-compatible message patterns: Use ICU message format concepts (plural/select/selectordinal) to support grammar differences per locale.
  • CLDR-driven pluralization and locale-aware formatting: Apply CLDR plural categories and format dates, numbers, currencies, lists, and relative time via Intl.
  • RTL and multilingual SEO readiness: Support RTL using the correct HTML dir/lang handling plus CSS logical properties, and generate hreflang tags (including x-default).
  • Locale negotiation strategies: Resolve locale from URL paths, cookies, Accept-Language, and fallbacks while keeping SSR behavior correct.
  • Translation workflow management: Organize namespaces, avoid common key pitfalls, and plan extraction and coverage checks to prevent missing strings.

Use when you are adding multi-language support, implementing pluralization or gender-aware messages, formatting by locale, handling RTL layout correctly, configuring locale detection, setting hreflang SEO tags, or managing translation workflows.

Quick Start

Ask the AI to recommend an i18n approach for your app (Paraglide vs i18next) and outline a locale strategy, RTL handling, plural/select message patterns, and hreflang tag setup for your supported languages.

Frequently Asked Questions about localization-engineer

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

FAQPage Schema
How do I implement i18n pluralization and locale-aware formatting in my application?▼

Implement i18n pluralization and locale-aware formatting by applying ICU message syntax for plural and select rules, and use Intl-based formatting for dates, numbers, and currencies driven by CLDR plural categories. This ensures correct grammar and localized rendering per locale.

What is the best way to handle RTL layout and multilingual SEO for supported languages?▼

Handle RTL layout and multilingual SEO by setting correct HTML dir and lang attributes, applying CSS logical properties for layout direction, and generating hreflang tags including x-default. This approach ensures proper visual rendering and search engine indexing across languages.

How does locale negotiation work for SSR and client-side rendering?▼

Locale negotiation resolves the user locale deterministically from URL paths, cookies, and Accept-Language headers with defined fallbacks. This strategy maintains correct locale detection behavior across both server-side and client-side rendering workflows.

Can I use ICU message format patterns for gender-aware and selectordinal messages?▼

Yes, you can use ICU message format patterns including plural, select, and selectordinal to support grammar differences per locale. ICU syntax enables robust gender-aware messages and ordinal numbering for comprehensive multilingual application support.

How do I manage translation workflows and avoid missing strings in a multilingual app?▼

Manage translation workflows by organizing message namespaces, avoiding common key pitfalls, and planning extraction and coverage checks. This prevents missing strings and ensures complete translation coverage across your application's supported languages.

Related Skills

Explore More Software Engineering Skills→
nishchaydevnishchaydev

i18n-localization

Detect hardcoded strings and validate locale JSON key consistency across locales.

Community
Intermediate
capaas2capaas2

i18n-localization

Detect hardcoded user-facing strings and missing translation keys in React, Vue, and Python projects.

Community
Intermediate
allenlin90allenlin90
1

frontend-i18n

Implement type-safe frontend i18n workflows with Paraglide and @eridu/i18n.

Community
Intermediate
AbdullahmohammadarefAbdullahmohammadaref

i18n

Integrate next-intl or react-i18next for locale-aware text and formatting.

Community
Advanced