What problem does it solve? Setting up internationalization from scratch involves many decisions: which library to use, how to structure locale files, how to extract strings, and how to wire up a translation platform. This Skill scaffolds that entire infrastructure with consistent, config-driven defaults. ## Core Features & Use Cases - i18n Library Configuration: Set up i18next, react-intl, or FormatJS with language detection, fallback locale chains, and namespace organization. - String Extraction Tooling: Extract message IDs from source code, detect hardcoded strings, and enforce key naming conventions. - Locale File Scaffolding: Generate locales/{locale}/{namespace}.json directory structures with default common and errors namespaces. - Translation Workflow Setup: Configure Crowdin or Lokalise projects with CI integration for translation file sync. - Use Case: You are starting a new React app that must ship in English and French. Invoke this Skill to install react-i18next, scaffold the locale directory structure, and configure a Crowdin GitHub Action for ongoing translation sync. ## Quick Start Set up internationalization for my React project using i18next with English and French locales and a Crowdin translation workflow.
