i18n-localization

Internationalization and localization patterns for multi-language app support. Internationalization (i18n) and Localization (L10n) best practices. Before shipping: This skill is applicable to execute the workflow or actions described in the overview. - Covers core i18n concepts, implementation patterns for React, Next.js, and Python, and file structure organization for managing translations across locales - Includes best practices for using translation keys, namespacing, pluralization, date/number formatting, and ICU message format to avoid common pitfalls - Provides RTL (right-to-left) layout guidance using CSS logical properties for languages like Arabic and Hebrew - Includes a hardcoded string detection script to identify missing translations and ensure all user-facing text uses translation keys - Use translation keys, not raw text - Namespace translations by feature - Support pluralization - Handle date/number formats per locale - Plan for RTL from the start - Use ICU message format for complex strings - Hardcode strings in components - Concatenate translated strings - Assume text length (German is 30% longer) - Forget about RTL layout - Mix languages in same file - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for...