i18n-localization

Detect hardcoded strings in React, Vue, and Python codebases.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill i18n-localization-brunosantanadeveloper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-localization
Source: https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit/tree/main/skills/i18n-localization
Command: npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill i18n-localization-brunosantanadeveloper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Detects hardcoded strings in codebases to enforce localization readiness and prevent post-hoc translations from being missed.

Core Features & Use Cases

  • Locale completeness checks across JSON/PO files to ensure translation keys align between languages.
  • Code-audit for i18n usage in React, Vue, and Python projects, flagging missing translations and unsafe hardcoded text.
  • Lightweight tooling that can be integrated into CI pipelines to enforce localization standards.

Quick Start

Run the i18n checker on your project to detect hardcoded strings and verify locale keys.

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

To detect hardcoded strings in React or Vue projects, an i18n audit tool scans your codebase and flags unsafe hardcoded text. This enforces localization readiness by identifying unextracted strings before translation begins.

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

Checking locale completeness across JSON and PO files involves scanning them to ensure translation keys align between languages. A locale audit engine validates these files and reports missing translations with structured output.

Can I integrate i18n static analysis into my CI pipeline?

Yes, you can integrate i18n static analysis into CI pipelines to enforce localization standards automatically. Running a locale audit engine on your code and locale files provides structured output to fail builds when missing translations or hardcoded text are found.

How do I validate locale keys in a Python project for missing translations?

Validating locale keys in Python requires auditing i18n usage to compare code strings against locale files. A locale audit engine surfaces missing translations and flags unsafe hardcoded text, ensuring full localization readiness.

What is the best way to enforce i18n best practices across multiple frameworks?

The best way to enforce i18n best practices across React, Vue, and Python is using a static analysis tool that audits code and locale files together. This detects hardcoded text and validates keys to prevent missed translations.