i18n-localization

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

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/oalansilva/crypto --skill i18n-localization-oalansilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-localization
Source: https://github.com/oalansilva/crypto/tree/main/.agent/skills/i18n-localization
Command: npx skills add https://github.com/oalansilva/crypto --skill i18n-localization-oalansilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hardcoded strings and missing translations slow down localization and degrade user experience across locales.

Core Features & Use Cases

  • Detect hardcoded strings across React, Vue, and Python code bases.
  • Compare locale keys and validate translation coverage across locales.
  • Generate or validate locale files to ensure consistent UI text across languages.

Quick Start

Configure the checker for your project and run it to scan your codebase and locale files.

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 or Vue codebase?

To find hardcoded strings in React or Vue codebases, scan source files for i18n usage patterns. This identifies untranslated text and missing translation keys to ensure consistent UI localization across locales.

What is i18n localization and why do missing translations degrade user experience?

i18n localization is the process of adapting software for different languages. Missing translations cause inconsistent UI text across locales, which degrades user experience and slows down the localization workflow.

How do I validate translation coverage across multiple JSON and PO locale files?

Validate translation coverage by comparing locale keys across JSON and PO files in your locales directory. Scanning source files and locale files reports structured gaps to ensure consistent translation coverage.

Does this i18n localization approach work with Python projects?

Yes, this i18n localization approach works with Python projects. It scans Python source files for i18n usage patterns and locates locale files scattered in locales directories to report translation gaps.

What is the best way to eliminate hardcoded UI text before localization?

The best way to eliminate hardcoded UI text is scanning codebases for i18n usage patterns and comparing locale keys. This detects untranslated strings and reports missing translations with a structured output.