i18n-localization

Audits React, Vue, Python codebases for hardcoded strings and missing translations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This guide helps identify hardcoded strings and missing translations to strengthen internationalization in software projects.

Core Features & Use Cases

  • Detect hardcoded strings in React, Vue, and Python codebases.
  • Check locale files for missing keys and ensure consistency across languages.
  • Assess RTL readiness and provide guidance for proper localization patterns.

Quick Start

Run the i18n audit against your project to surface localization issues and remediation steps.

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 codebases?

To detect hardcoded strings in React and Vue codebases, you can run a static code audit that scans your source files to identify untranslated text and enforces i18n best practices by reporting inconsistencies for remediation.

What is the best way to check locale files for missing translation keys?

The best way to check locale files for missing translation keys is to perform a locale completeness audit that scans your files to ensure key consistency across languages and reports missing translations for remediation.

How do I audit my Python project for internationalization and RTL readiness?

You audit your Python project for internationalization and RTL readiness by scanning the codebase and locale files to assess translation coverage, identify missing keys, and provide guidance for proper right-to-left localization patterns.

Does this i18n localization audit require any external dependencies?

This i18n localization audit requires no external dependencies, allowing you to directly scan your codebase and locale files to surface translation issues and generate remediation steps without additional environment setup.