What problem does it solve?
Better i18n prevents fragile localization decisions by giving you one consistent playbook for SDK selection, CDN vs GitHub workflows, AI translation flows via MCP tools, CLI health checks, and the conventions that keep keys stable and translations publishable.
Core Features & Use Cases
- SDK and workflow selection: choose the right TypeScript SDK for your stack (Next.js, React, Vite, Remix, Expo/React Native, Core/headless, and server runtimes), and decide when to use CDN-only vs GitHub PR sync.
- AI-powered key and translation management (MCP): integrate translation key creation, updates, language proposals, pending-change review, and publishing through MCP tools with safety rules.
- CLI quality and release confidence: run scan, sync, check, and doctor to catch hardcoded strings, coverage gaps, naming inconsistencies, placeholder mismatches, and file-format issues before publishing.
Quick Start
Use the better-i18n skill to decide your exact localization setup and verify key naming, file format, locale normalization, and release flow for your project before you start implementing or publishing any i18n changes.