i18n-localization

Detect hardcoded strings and missing translations in React, Vue, Next.js, and Python projects.

Updated Mar 8, 2026

Search Tags:#audit #localization #translation #i18n #rtl #locale-files #hardcoded-strings

Ready to run

npx skills add https://github.com/darthlinuxer/dialectic-crew-ai --skill i18n-localization-darthlinuxer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: i18n-localization
Source: https://github.com/darthlinuxer/dialectic-crew-ai/tree/main/src/mcp/skills/i18n-localization
Command: npx skills add https://github.com/darthlinuxer/dialectic-crew-ai --skill i18n-localization-darthlinuxer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Detects hardcoded user-facing strings, missing translations, inconsistent locale keys, and common RTL issues so teams can ship fully localized interfaces with fewer regressions and manual checks.

Core Features & Use Cases

Automated scanning for hardcoded strings across React, Vue, Next.js, and Python source files.
Locale completeness checks that compare keys across JSON and PO files to surface missing or extra translations.
Practical guidance for file structure, RTL handling, and i18n best practices to reduce layout and formatting bugs.
Use Case: Run an audit before a release to locate untranslated strings, verify locale parity, and identify RTL adjustments required for new language support.

Quick Start

Run the included i18n_checker.py script against your project path to audit locale files and detect potential hardcoded strings.

Frequently Asked Questions about i18n-localization

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

FAQPage Schema

How do I detect hardcoded strings in React and Vue before a release?▼

Run an automated scan against your React, Vue, Next.js, or Python source files to detect hardcoded user-facing strings. This reveals untranslated UI text and missing translation keys before release preparation.

How do I check locale file completeness across JSON and PO translation files?▼

Check locale completeness by parsing JSON and PO files to compare translation keys across languages. This surfaces missing or extra translations, ensuring locale parity and full translation coverage.

Can I use this for Python localization audits and not just web frameworks?▼

Yes, Python localization audits are fully supported. The scanner detects hardcoded strings in Python source files and parses PO files, applying the same completeness checks used for web projects.

What is the best way to find missing i18n translations in a Next.js codebase?▼

The best way to find missing i18n translations is running an automated audit that scans Next.js source files for hardcoded strings and compares locale JSON files to report translation completeness.

Does the i18n audit detect RTL layout issues for new language support?▼

Yes, the i18n audit identifies common RTL issues and provides practical guidance for RTL handling. This reduces layout and formatting bugs when adding new language support to your interface.

Why do I have extra translation keys in some locale JSON files?▼

Extra translation keys occur when locale JSON files are not synchronized. The audit compares keys across all language files to surface inconsistencies, missing translations, and extra keys for cleanup.