better-i18n

Guides i18n architecture for SDK selection, CDN vs GitHub, and MCP translation workflows.

16|3|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/better-i18n/oss --skill better-i18n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: better-i18n
Source: https://github.com/better-i18n/oss/tree/main/skill
Command: npx skills add https://github.com/better-i18n/oss --skill better-i18n

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about better-i18n

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up localization architecture for a Next.js app using CDN translations?

To configure localization architecture for Next.js, select the appropriate TypeScript SDK, establish key conventions, and configure CDN versus GitHub sync workflows. You must normalize locales for CDN paths and apply singleton initialization rules to ensure production-safe translation publishing.

Can I use AI translation workflows via MCP for creating and updating localization keys?

AI translation workflows via MCP tools support translation key creation, updates, language proposals, and pending-change review. These MCP guardrails enforce safe key creation practices and publishing rules to prevent fragile localization decisions.

What is the best way to detect hardcoded strings and translation coverage gaps before publishing?

The best way to detect hardcoded strings and coverage gaps is running CLI health checks. CLI tools provide scan, sync, check, and doctor commands to catch naming inconsistencies, placeholder mismatches, and file-format issues before publishing translations.

Does the TypeScript SDK selection differ between React, Vite, and Expo projects?

TypeScript SDK selection differs across React, Vite, Remix, and Expo/React Native stacks. Choosing the right SDK for your specific framework ensures correct project identifier usage, locale handling, and integration patterns for modern TypeScript applications.

How do I prevent blank translation failure modes when syncing translations to a CDN?

Preventing blank translation failure modes requires CLI health verification and locale normalization for CDN paths. Running CLI doctor checks detects fallback and blank translation issues, ensuring your localization architecture maintains production-safe publishing workflows.