skills.rest
pckienuit
pckienuitCOMMUNITY
Explore all skills by this author →
GitHub

i18n-localization

Detect hardcoded user-facing strings and missing translation keys in React, Vue, and Python projects.

Updated Mar 30, 2026
Search Tags:#localization#code audit#i18n#translations#rtl#hardcoded strings
One-click install
npx skills add https://github.com/pckienuit/GameDev1 --skill i18n-localization-pckienuit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: i18n-localization
Source: https://github.com/pckienuit/GameDev1/tree/main/.cursor/skills/i18n-localization
Command: npx skills add https://github.com/pckienuit/GameDev1 --skill i18n-localization-pckienuit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps teams find hardcoded user-facing text and weak localization coverage before release, reducing translation bugs and making multilingual support easier to maintain.

Core Features & Use Cases

  • Hardcoded String Detection: Scans code for visible text that should be moved into translation keys.
  • Locale Coverage Checks: Compares JSON locale files to spot missing or extra translation keys.
  • Practical Use Case: Use it to audit a React, Vue, or Python app before launching in new markets and quickly identify untranslated UI copy.

Quick Start

Ask the skill to review your project for hardcoded strings and missing locale keys, then summarize the issues it finds.

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

You can find hardcoded strings by scanning your React or Vue source files for visible text that should be moved into translation keys. This process detects untranslated UI copy before release.

How do I check for missing translation keys in JSON locale files?▼

Checking for missing translation keys involves comparing JSON locale files to spot missing or extra entries. This validates your i18n coverage and highlights untranslated text.

Does this i18n localization audit work with Python projects?▼

Yes, this i18n localization audit works with Python projects. It uses standard-library file scanning and regex pattern matching to validate translation usage without external dependencies.

What is the best way to review my app for RTL-aware interface issues?▼

The best way to review for RTL-aware interface issues is to audit your application code for hardcoded user-facing strings and missing translation coverage. This catches localization bugs early.

Do I need external dependencies to scan my code for missing locale keys?▼

No, you do not need external dependencies to scan for missing locale keys. The audit relies on standard-library file scanning, regex pattern matching, and JSON locale inspection.

When should I audit my application for hardcoded user-facing text?▼

You should audit for hardcoded user-facing text before launching in new markets. Finding weak localization coverage early reduces translation bugs and makes multilingual support easier to maintain.

Related Skills

Explore More Software Engineering Skills→
ag47-ptag47-pt
1

i18n-localization

Detect hardcoded strings and incomplete translations in application code.

Community
Intermediate
capaas2capaas2

i18n-localization

Detect hardcoded user-facing strings and missing translation keys in React, Vue, and Python projects.

Community
Intermediate
Oscar-Ivan-SalasOscar-Ivan-Salas

i18n-localization

Audit React, Next.js, Vue, and Python code for hardcoded UI strings and i18n gaps.

Community
Intermediate
berkcangumusisikberkcangumusisik
11

i18n-check

Scan React, Vue, and Angular files to replace hardcoded strings with i18n keys.

Community
Intermediate