i18n-localizationlisted
Install: claude install-skill mahdy-gribkov/arcana
# Internationalization and localization
Scope: making a web app work in more than one language and direction. Read the existing setup first (the i18n library and version in
`package.json`, the message folder, the routing config) and extend it; do not add a second i18n library.
## Where to look
| Task | Read |
|---|---|
| next-intl routing, proxy.ts, layouts, locale switcher, loading messages, typed keys | [references/next-intl-setup.md](references/next-intl-setup.md) |
| ICU plural and select, rich text, dates, numbers, currency | [references/icu-and-formatting.md](references/icu-and-formatting.md) |
| Hebrew, Arabic, or other RTL layouts, logical CSS, Tailwind | [references/rtl-layout.md](references/rtl-layout.md) |
Read the file that matches the task before writing code. The core rules below always apply.
Related skills: `nextjs-16` owns `proxy.ts` and routing in general, `seo-meta` owns metadata (this skill covers only `hreflang`),
`accessibility-wcag` owns `lang` on inline foreign-language text.
## Core rules
1. **No user-visible string in code.** Every label, error, placeholder, `aria-label`, and page title comes from a message file.
2. **One message per sentence.** Never concatenate fragments or build plurals with a ternary. Use ICU `plural` and `select`.
3. **Always include the `other` branch** in plural and select messages.
4. **Format with Intl.** Dates, numbers, currency, lists, and relative times go through `Intl` or the library formatter, never `toFixed` or