i18n-localization

Audit codebases for hardcoded strings and verify locale file coverage.

Updated Jan 22, 2026

Search Tags:#localization #code-quality #i18n #translations #locale #ParaglideJS #localization-check

Ready to run

npx skills add https://github.com/emelleby/tc-vsme --skill i18n-localization-emelleby

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: i18n-localization
Source: https://github.com/emelleby/tc-vsme/tree/main/.agent/skills/i18n-localization-paraglidejs
Command: npx skills add https://github.com/emelleby/tc-vsme --skill i18n-localization-emelleby

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Internationalized software requires avoiding hardcoded strings and maintaining complete locale coverage. This Skill helps teams detect hardcoded text, verify translation keys, and validate locale files across projects to ensure consistent localization and RTL support.

Core Features & Use Cases

Hardcoded string detection across Paraglide JS, React i18n, Vue i18n, and Python gettext workflows.
Locale validation to ensure translation keys exist across languages and RTL readiness.
Guidance & automation hooks to improve internationalization workflows in web and backend apps.

Quick Start

Run the i18n checker against your project: python scripts/i18n_checker.py <path-to-your-project>

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 my codebase for internationalization?▼

Detect hardcoded strings by running a localization audit against your project to surface untranslated text. This checker scans codebases to identify hardcoded text and verifies translation coverage across web apps and APIs.

Can I verify locale files for missing translation keys across React or Vue i18n?▼

Verify locale files by validating translation key presence and consistency across different languages. The checker supports React i18n, Vue i18n, and Python gettext workflows to surface missing or extra keys.

Does the localization checker support Paraglide JS workflows?▼

Paraglide JS workflows are fully supported for hardcoded string detection and translation verification. The tool audits codebases using Paraglide JS alongside React, Vue, and Python gettext to ensure complete locale coverage.

What is the best way to check for RTL-related localization issues in multi-language products?▼

Check for RTL-related localization issues by auditing your locale files and translation keys for consistency. The checker highlights RTL readiness and validates locale coverage to ensure proper multi-language product support.

How do I validate locale file consistency across multiple languages?▼

Validate locale file consistency by auditing translation keys to ensure they exist across all target languages. The tool surfaces missing or extra keys and verifies translation coverage across web apps and multi-language products.