i18n-localization

Detect hardcoded strings and validate locale files in React, Vue, and Python codebases.

Updated Jan 21, 2026

Search Tags:#react #python #vue #localization #translation #i18n #code-audit

Ready to run

npx skills add https://github.com/ollieb89/orchestrator --skill i18n-localization-ollieb89

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: i18n-localization
Source: https://github.com/ollieb89/orchestrator/tree/main/.cursor/skills/i18n-localization
Command: npx skills add https://github.com/ollieb89/orchestrator --skill i18n-localization-ollieb89

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Identify hardcoded strings and missing translations across React, Vue, and Python codebases to ensure localization readiness and reduce runtime localization errors.

Core Features & Use Cases

Detect hardcoded strings in frontend and backend files.
Validate locale files for consistency, completeness, and RTL readiness.
Generate guidance to fix i18n gaps across projects and CI pipelines.

Quick Start

Run the i18n_checker.py script against your project to detect hardcoded strings and missing translations.

Frequently Asked Questions about i18n-localization

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

FAQPage Schema

How do I find hardcoded strings in my React and Vue codebase?▼

To find hardcoded strings in React and Vue codebases, scan your project files to detect text bypassing locale files. This process exposes translation gaps by validating locale schemas and reporting missing keys for remediation.

What is the best way to check for missing translations across Python projects?▼

Checking for missing translations across Python projects involves scanning code to validate locale file consistency and completeness. This identifies extra or missing keys and maintains localization coverage across the application.

How do I validate locale files for RTL readiness in my application?▼

Validating locale files for RTL readiness involves checking locale schemas to ensure right-to-left language support. Scanning code and locale files exposes i18n gaps and confirms translation workflows are prepared for RTL languages.

Can I enforce i18n coverage in my CI pipeline?▼

You can enforce i18n coverage in CI pipelines by running localization checks against your project. This detects hardcoded strings and validates locale schemas to ensure translation completeness and prevent runtime localization errors.

How do I audit key existence in locale files for frontend frameworks?▼

Auditing key existence in locale files for frontend frameworks requires scanning code to validate locale schemas. This reports missing or extra keys, ensuring translation workflows maintain complete localization coverage.