i18n-checker

Detect hardcoded user-facing strings in UI components and suggest i18n replacements.

7|Updated Mar 11, 2026

Search Tags:#react #localization #code audit #i18n #internationalization #hardcoded strings

Ready to run

npx skills add https://github.com/kaelig/react-craft --skill i18n-checker-kaelig

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: i18n-checker
Source: https://github.com/kaelig/react-craft/tree/main/react-craft/examples/custom-skills/i18n-checker
Command: npx skills add https://github.com/kaelig/react-craft --skill i18n-checker-kaelig

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies user-facing strings in code that have not been internationalized, ensuring applications are ready for global audiences.

Core Features & Use Cases

Hardcoded String Detection: Scans code for plain text strings that should be managed by an i18n framework.
i18n Framework Integration: Suggests replacements using common frameworks like react-intl and i18next.
Use Case: Audit a React component to ensure all user-visible text, like button labels and error messages, is internationalized.

Quick Start

Run the i18n-checker skill to find hardcoded strings in the project's UI components.

Frequently Asked Questions about i18n-checker

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

FAQPage Schema

How do I find hardcoded strings in React components for internationalization?▼

To find hardcoded strings for internationalization in React components, scan JSX text content, placeholders, aria-labels, titles, alt text, button text, error messages, and headings. The process filters out technical strings and comments, identifying plain text that requires i18n framework management.

What is hardcoded string detection in UI components?▼

Hardcoded string detection in UI components is the process of scanning code for plain text strings that should be managed by an internationalization framework. It identifies user-facing text like button labels and error messages that have not been internationalized for global audiences.

Does the hardcoded string checker support react-intl and i18next?▼

Yes, the hardcoded string checker supports react-intl and i18next. It detects plain text strings in UI components and suggests replacements using these common internationalization frameworks to ensure applications are ready for global audiences.

How do I audit a React component for un-internationalized user-facing text?▼

To audit a React component for un-internationalized user-facing text, run a scan against JSX content, placeholders, and aria-labels. This detects hardcoded strings and suggests appropriate replacements using the project's existing i18n framework.

What strings are filtered out during hardcoded string detection?▼

During hardcoded string detection, technical strings, i18n keys, and comments are filtered out. This ensures the scan focuses exclusively on user-facing plain text content that requires internationalization, ignoring non-user-facing code elements.