skills.rest
capaas2
capaas2COMMUNITY
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 Apr 4, 2026
Search Tags:#react#localization#i18n#translations#rtl#hardcoded strings#locale files
One-click install
npx skills add https://github.com/capaas2/Site-teste --skill i18n-localization-capaas2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: i18n-localization
Source: https://github.com/capaas2/Site-teste/tree/main/.agent/skills/i18n-localization
Command: npx skills add https://github.com/capaas2/Site-teste --skill i18n-localization-capaas2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you identify hardcoded user-facing text and verify translation coverage so your product can support multiple languages without shipping inconsistent or missing copy.

Core Features & Use Cases

  • Hardcoded String Detection: Scans React, Vue, and Python code for visible text that should be moved into translation keys.
  • Locale Coverage Checks: Compares JSON locale files to spot missing or mismatched keys across languages.
  • Best-Practice Guidance: Reinforces proper i18n patterns such as namespaced translation files, pluralization, date and number formatting, and RTL support.
  • Use Case: Run it on a web app before release to catch untranslated buttons, labels, error messages, and incomplete locale files.

Quick Start

Ask the skill to audit your project for hardcoded strings and missing translations.

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 React and Vue components before shipping?▼

To find hardcoded strings in React and Vue, scan your application code for visible text that should be moved into translation keys. This process detects untranslated buttons, labels, and error messages prior to release.

What is the best way to check for missing translations across JSON locale files?▼

Checking for missing translations involves comparing JSON locale files to spot mismatched or missing keys across languages. This validates translation coverage and ensures fallback readiness for your multilingual application.

Does this i18n localization audit work with Next.js and Python projects?▼

Yes, i18n localization audits work with Next.js and Python projects. The scanning process applies to React, Vue, Next.js, and Python projects with multilingual interfaces to detect hardcoded strings and validate locale coverage.

How do I validate pluralization support and RTL-friendly implementation patterns in my app?▼

Validating pluralization support and RTL-friendly patterns involves scanning code and JSON translation resources to reinforce proper i18n patterns. This checks pluralization, date and number formatting, and RTL implementation in your application.

Why do I need to scan code and JSON translation resources for locale-aware UI audits?▼

Scanning code and JSON translation resources is needed for locale-aware UI audits to identify hardcoded user-facing text and verify translation coverage. This ensures your public web app or SaaS product supports multiple languages without missing copy.

Related Skills

Explore More Software Engineering Skills→
darthlinuxerdarthlinuxer

i18n-localization

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

Community
Intermediate
kmshdevkmshdev
1

swift-localization

Implement iOS localization with String Catalogs and LocalizedStringResource.

Community
Advanced
hadimiftahulfhadimiftahulf

i18n-localizer

Enforce translation keys, pluralization, locale formatting, and RTL layout support.

Community
Intermediate
nextcnextc
2

flutter-l10n-status

Compute per-locale translation coverage for Flutter ARB files.

Official
Intermediate