i18n Readiness Review Skill
Localizing a product that isn't internationalized fails expensively — translators hit hard-coded
strings, layouts break on longer languages, dates show in the wrong format, and RTL shatters the UI.
i18n is the engineering groundwork; localization is the content. This skill audits whether the product
is ready, so you fix the foundations before paying to translate into the cracks.
Required Inputs
Ask for these only if they aren't already provided:
- The product — web/app/codebase, stack/framework (i18n tooling differs).
- Target languages — especially if any need RTL (Arabic/Hebrew), CJK (Chinese/Japanese/Korean), or are long (German/Finnish).
- What you can share — code snippets, UI screenshots, or a description of how strings/formatting are handled today.
Output Format
i18n Readiness: [product]
A readiness audit across the dimensions that break localization, each with status (🟢 ready / 🟡 partial / 🔴 blocker) and the fix:
| Dimension |
Check |
Status |
Fix |
| String externalization |
no user-facing text hard-coded; all in resource files / i18n keys |
|
move strings to a catalog; no concatenated sentences |
| Formatting |
dates, numbers, currency, plurals via locale-aware libs (Intl/ICU) |
|
use Intl/ICU; never string-format dates |
| Pluralization |
plural rules handled (not count + " items") |
|
ICU plural categories (some langs have 4–6) |
| Layout/expansion |
UI tolerates ~+30–40% text length; no fixed-width truncation |
|
flexible layouts, no text baked into images |
| Encoding |
UTF-8 throughout; CJK renders |
|
UTF-8 end to end |
| RTL |
layout mirrors for right-to-left scripts |
|
logical CSS properties, dir attribute |
| Locale plumbing |
locale selection, fallback, and persistence exist |
|
a locale resolver + fallback chain |
| Assets/content |
images with text, examples, names are swappable |
|
externalize locale-specific assets |
Prioritised fixes — the blockers (🔴) first (hard-coded strings, no Intl formatting, broken RTL), then 🟡s. These must land before translation begins, or you translate into a broken foundation.
Verdict — ready to localize / fix-blockers-first / not yet, in one line.
Quality Checks
Anti-Patterns
Based On
Internationalization engineering practice — string externalization, ICU/Intl formatting & plurals, text expansion, RTL, UTF-8.
1---2name: i18n-readiness-review-23description: "Review a product/codebase for internationalization readiness before you localize. Use when asked if a product is ready to localize, to review i18n readiness, find hard-coded strings/locale bugs, or prep for going multilingual. Produces a readiness audit — externalized strings, locale-aware formatting, layout/expansion, encoding/RTL, and a prioritised list of i18n fixes to make before translation starts."4homepage: https://mohitagw15856.github.io/pm-claude-skills/skill/i18n-readiness-review.html5metadata:6 source: https://skillmd.com/skills/mohitagw15856/i18n-readiness-review-27 openclaw:8 emoji: 🌐9---1011# i18n Readiness Review Skill1213Localizing a product that isn't *internationalized* fails expensively — translators hit hard-coded14strings, layouts break on longer languages, dates show in the wrong format, and RTL shatters the UI.15i18n is the engineering groundwork; localization is the content. This skill audits whether the product16is ready, so you fix the foundations *before* paying to translate into the cracks.1718## Required Inputs1920Ask for these only if they aren't already provided:2122- **The product** — web/app/codebase, stack/framework (i18n tooling differs).23- **Target languages** — especially if any need RTL (Arabic/Hebrew), CJK (Chinese/Japanese/Korean), or are long (German/Finnish).24- **What you can share** — code snippets, UI screenshots, or a description of how strings/formatting are handled today.2526## Output Format2728### i18n Readiness: [product]2930A readiness audit across the dimensions that break localization, each with status (🟢 ready / 🟡 partial / 🔴 blocker) and the fix:3132| Dimension | Check | Status | Fix |33|---|---|---|---|34| **String externalization** | no user-facing text hard-coded; all in resource files / i18n keys | | move strings to a catalog; no concatenated sentences |35| **Formatting** | dates, numbers, currency, plurals via locale-aware libs (Intl/ICU) | | use Intl/ICU; never string-format dates |36| **Pluralization** | plural rules handled (not `count + " items"`) | | ICU plural categories (some langs have 4–6) |37| **Layout/expansion** | UI tolerates ~+30–40% text length; no fixed-width truncation | | flexible layouts, no text baked into images |38| **Encoding** | UTF-8 throughout; CJK renders | | UTF-8 end to end |39| **RTL** | layout mirrors for right-to-left scripts | | logical CSS properties, dir attribute |40| **Locale plumbing** | locale selection, fallback, and persistence exist | | a locale resolver + fallback chain |41| **Assets/content** | images with text, examples, names are swappable | | externalize locale-specific assets |4243**Prioritised fixes** — the blockers (🔴) first (hard-coded strings, no Intl formatting, broken RTL), then 🟡s. These must land **before** translation begins, or you translate into a broken foundation.4445**Verdict** — ready to localize / fix-blockers-first / not yet, in one line.4647## Quality Checks4849- [ ] Checks string externalization (the #1 blocker) — no hard-coded or concatenated UI text50- [ ] Verifies locale-aware formatting (Intl/ICU) for dates, numbers, currency, plurals51- [ ] Assesses layout expansion (+30–40%) and RTL if a target needs it52- [ ] Confirms UTF-8 / CJK encoding end to end53- [ ] Prioritises blockers to fix *before* translation starts54- [ ] Ends with a clear ready / not-ready verdict5556## Anti-Patterns5758- [ ] Do not start translating before i18n is ready — you'll translate into hard-coded strings and broken layouts59- [ ] Do not concatenate sentence fragments — word order differs by language; translate whole strings with placeholders60- [ ] Do not string-format dates/numbers — use Intl/ICU, or every locale shows them wrong61- [ ] Do not assume text length — German/Finnish expand; fixed-width UI truncates and clips62- [ ] Do not ignore RTL until late — retrofitting right-to-left into a left-to-right layout is a rebuild, not a tweak6364## Based On6566Internationalization engineering practice — string externalization, ICU/Intl formatting & plurals, text expansion, RTL, UTF-8.