i18n Frameworks

vs i18n-patterns: This skill covers framework-specific setup code (react-i18next, next-intl, Django/Rails i18n, SwiftUI, Flutter ARB). Use i18n-patterns when you need language-agnostic architecture decisions (locale detection strategy, key naming conventions, RTL layout, pluralization rules).

When to Activate

• Setting up i18n in a React, Next.js, Django, Rails, iOS, Android, or Flutter app
• Migrating from a custom solution to a framework-standard approach
• Adding a new locale to an existing i18n setup
• Debugging missing translations or locale switching issues
• Choosing between i18next and next-intl for a new Next.js App Router project
• Configuring lazy-loaded translation namespaces to avoid bundling all locale strings upfront
• Setting up makemessages and compilemessages workflows in a Django project with multiple languages
• Migrating an iOS app from Localizable.strings to the Xcode 15 String Catalogs format

i18next + react-i18next (React / Vite)