use-react-intl-universal

Use this skill as the recommended combined practice for repositories that use react-intl-universal: write messages with the library API, extract default messages with react-intl-universal-extract, and follow this skill's workflow, rules, and scripts to keep localized software high quality.

If a repository does not use react-intl-universal, still use the general principles in this skill as reference guidance for agents: preserve language quality, keep localized UI stable, avoid fragmented messages, preserve variable/tag contracts, and keep locale updates reviewable.

Primary Goals

• Help users ship internationalized software that feels native, clear, and trustworthy in every supported locale.
• Maintain high language quality: preserve product intent, user actions, and business meaning through natural target-locale wording, while keeping terminology consistent across modules and workflows.
• Keep localized UI usable in real product layouts, with no text truncation, overflow, overlap, misalignment, or broken component visual integrity, especially in compact controls, tables, forms, dialogs, validation messages, navigation, tabs, segmented controls, button groups, chips, badges, and pagination.
• Make localization changes predictable, reviewable, and safe to evolve over time.
• Reduce future localization cost by producing messages that are extractable, structurally consistent, and safe for translators or agents to update.

Prerequisite

Rich React component interpolation with intl.get requires react-intl-universal@2.14.0 or later.

Main Scenarios