Better I18N

Guides all Better i18n integration decisions — SDK selection (Next.js, React, Expo, Swift, Flutter, Remix), CDN vs GitHub workflow, AI-powered translation management via MCP tools, CLI health checks (scan, doctor, sync), Content CMS (localized models, entries, custom fields), file format conventions (flat / nested / namespaced), key naming, publish flows, and quality analytics. Use whenever building, modifying, or reviewing any localization feature — including i18n setup, adding languages, managing translation keys, publishing, or integrating AI workflows. Use when this capability is needed.

tomevault-io Updated

File contents

tomevault-io/skills-registry/tree/main/better-i18n--oss--better-i18n commit 5c9d9406c1

Frequently asked questions

npx skillmds@latest add tomevault-io/better-i18n