i18n

To add a new translation key for internationalization, use the i18n skill to enforce strict rules against hardcoding strings. It guides you through using formatMessage with a specific translation key naming pattern to maintain translation integrity and consistency globally.

Managing application locales and handling locale fallbacks is streamlined through automatic locale detection and fallback mechanisms. This ensures text is correctly translated and displayed according to user locale preferences, maintaining a consistent global user experience.

You should not modify auto-generated translation files because the i18n skill enforces strict rules against it to maintain translation integrity. Modifying these files breaks the automated internationalization process and compromises the consistency of translation key naming patterns.

To ensure all user-facing text is properly internationalized when developing a new feature, use the i18n skill. It provides guidelines and enforces best practices for adding, updating, and using translations via formatMessage, preventing hardcoded strings.

To maintain consistency, you must adhere to a specific translation key naming pattern required by the i18n skill. This pattern is enforced during the addition of new translations to ensure text is correctly translated and displayed according to user locale preferences.

Yes, this internationalization approach works with automatic locale detection. The i18n skill supports automatic locale detection and fallback mechanisms, ensuring text is correctly translated and displayed according to user locale preferences without requiring manual locale configuration.