i18n-localization

Run the i18n checker script against your project path to scan JSX files for text directly in elements, title, placeholder, and aria-label attributes. Files already using t() or useTranslation are recognized as properly internationalized.

The checker loads JSON files from locales, translations, lang, or i18n directories, flattens nested keys, and compares each language against the base language. It reports missing and extra keys per namespace.

next-intl integrates with Next.js routing and server components using useTranslations with namespaces, while react-i18next uses the t() function with useTranslation. Both are supported patterns in this Skill's guidance.

Yes, it scans Python files for hardcoded strings in print statements, raise calls, and Flask flash messages. It recognizes gettext patterns like _() and gettext() as proper internationalization, and also finds .po locale files.

Use CSS logical properties such as margin-inline-start and padding-inline-end instead of margin-left and padding-right. For directional icons, apply transform: scaleX(-1) under the [dir="rtl"] selector.

Regex-based detection can produce false positives on capitalized text that is not user-facing and may miss dynamically constructed strings. The script limits analysis to 50 code files and skips test, build, and dependency directories.