internationalization-at-scale_skill

This skill enables scalable internationalization with code-splitting and ICU support, delivering sub-second locale switches and RTL-aware layouts.

HTML

1

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill harborgrid-justin/lexiflow-premium --skill internationalization-at-scale

SKILL.md819 B

Overview

This skill shows how to implement performant internationalization pipelines for large web apps, focusing on code-splitting, ICU message support, and RTL handling. It is designed for teams building high-performance, legal-grade applications that require sub-second locale switching and correct bidirectional layouts. The guidance emphasizes practical patterns, measurable acceptance criteria, and avoidance of common scaling pitfalls.

How this skill works

The skill demonstrates a runtime that dynamically loads locale-specific chunks on demand to avoid shipping all translations up front. It integrates an ICU message parser and runtime interpolation to support pluralization, gender, and complex formatted messages. It also outlines layout mirroring and CSS strategy to switch between LTR and RTL without visual jank.

When to use it

Large single-page apps where shipping full translation bundles hurts performance
Applications requiring advanced ICU features (plurals, select, nested formatting)
Products that must support RTL languages and preserve layout integrity
Systems that synchronize local source strings with translation services
Legal or compliance platforms where accurate localized messaging is critical

Best practices

Code-split translations by locale and feature to prevent waterfall loads
Use an ICU-compliant library or compile-time validation for message correctness
Preload only likely locales and lazy-load less-frequent ones on first use
Apply logical CSS mirroring (dir attribute) and avoid hardcoded directional styles
Automate string extraction and maintain a canonical source to reduce drift

Example use cases

Switch user locale sub-second by fetching a small locale chunk and swapping message catalog
Render complex legal notices using ICU messages with pluralization and gender variants
Mirror forms, navigation, and iconography when switching to Arabic or Hebrew
Batch-extract UI strings and push them to a translation management system for translators
Prevent waterfall by batching locale requests and caching decoded messages

FAQ

Prepare style rules for both directions, swap the dir attribute early, and preload critical fonts and locale-specific resources to prevent reflow.

Can ICU messages be validated at build time?

Yes — validate ICU syntax during CI using a parser to catch errors before deployment and fail builds on invalid messages.

How to prevent translation bundle waterfalls?

Group messages by route/feature, lazy-load those bundles, and use runtime caching with ETag or service-worker strategies.