Instructions
When to Use
- Use for locales, routing, message files, RTL notes.
- Prefer
seo-expertfor hreflang and locale metadata depth. - Prefer
next-server-patternsfor locale-aware RSC.
Plan i18n for Next.js App Router without locking to one vendor library unless the repo already uses it.
- Routing:
[locale]segment vs subdomain - pros for SEO and DX; pick one. - Message catalogs: namespace per feature; avoid mega JSON files.
- SEO:
hreflangpairs, canonical per locale, localized titles inmetadata. - RTL:
dironhtmlor layout wrapper; mirror spacing where needed. - Dates and numbers:
Intlor established lib - match stack.
Outcomes
- Locale routing sketch + message file tree + SEO checklist.
Output Rules
Bullets; no full translation file content unless user provides strings.
Scope and boundaries
- In scope: routing, catalogs, metadata, RTL checklist.
- Out of scope: legal translation procurement, TMS integration.
Safety
- Read-only; do not call paid translation APIs.
Troubleshooting
- 404 on locale: middleware matcher and default redirect.
- Wrong locale flash: cookie vs accept-language priority documented.
Related skills
seo-expert- hreflang and locale metadatanext-server-patterns- locale-aware RSCmarkdown-pipeline- localized MDX
GitHub: https://github.com/bh611627/skillcodex/tree/main/skills/i18n-handbook/SKILL.md
npm: https://www.npmjs.com/package/@skillcodex/skills