i18n

Detect i18n anti-patterns in frontend PRs modifying translated UI strings.

Updated May 15, 2026

Search Tags:#testing #code review #frontend #i18n #internationalization #pluralization #locale formatting

Ready to run

npx skills add https://github.com/mattnowdev/super-review --skill i18n-mattnowdev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: i18n
Source: https://github.com/mattnowdev/super-review/tree/main/skills/i18n
Command: npx skills add https://github.com/mattnowdev/super-review --skill i18n-mattnowdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Internationalization bugs make your UI inconsistent across languages, break translations, and can cause incorrect user-facing formatting that hurts trust and usability.

Core Features & Use Cases

Identifies i18n anti-patterns: flags hardcoded user-visible strings that bypass the translation layer, broken pluralization logic, and concatenated translated fragments.
Prevents locale formatting regressions: detects locale-naive date/number/currency formatting and locale-sensitive sorting mistakes.
Protects correctness through safer QA: flags tests that assert on translated UI text and encourages stable selectors or behavior-based assertions.

Quick Start

Load this i18n review reference when your project uses i18n and the PR changes client-facing strings or locale-sensitive formatting.

Frequently Asked Questions about i18n

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I catch internationalization regressions in frontend pull requests?▼

To catch internationalization regressions, review frontend pull requests to detect hardcoded strings, broken pluralization, and locale-naive formatting before they ship to multi-language applications.

What is the best way to prevent locale-naive date and currency formatting?▼

Preventing locale-naive date and currency formatting requires detecting unlocalized rendering logic during code review to ensure date, number, and currency outputs adapt correctly to active locales.

How do I enforce translation key parity and ICU pluralization in my UI?▼

Enforcing translation key parity and ICU pluralization involves reviewing translated UI strings to ensure correct use of translation functions and prevent concatenated or broken pluralized messages.

Does this i18n review process handle RTL-sensitive layout and locale-sensitive sorting?▼

Yes, this i18n review process handles RTL-sensitive layout and locale-sensitive sorting by detecting directionality issues and sorting mistakes that cause user-visible localization regressions.

Why should I avoid asserting on translated UI text in localization tests?▼

Asserting on translated UI text creates unstable tests; instead, flag these assertions and use stable selectors or behavior-based testing to protect correctness through safer QA.

When do I need to run an i18n anti-pattern check on my codebase?▼

You need an i18n anti-pattern check when a pull request adds or modifies translated UI strings, pluralized messages, currency rendering, or localization-aware tests in a multi-language application.