i18n-localization

Detect hardcoded strings and missing translation keys in locale JSON files.

Updated May 19, 2026
One-click install
npx skills add https://github.com/TimeKast/AgendaInteligente --skill i18n-localization-timekast
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-localization
Source: https://github.com/TimeKast/AgendaInteligente/tree/main/.agent/skills/i18n-localization
Command: npx skills add https://github.com/TimeKast/AgendaInteligente --skill i18n-localization-timekast

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you implement internationalization (i18n) and localization (l10n) practices by identifying hardcoded user-facing strings, ensuring locale files are complete, and preparing your UI for right-to-left (RTL) languages.

Core Features & Use Cases

  • Hardcoded string detection: Finds likely hardcoded UI text in React/Vue/Python code so translations can be added consistently.
  • Locale completeness checks: Verifies that multiple locale JSON files share matching translation keys across languages and namespaces.
  • RTL readiness guidance: Supports planning for RTL behaviors using CSS logical properties and direction-aware styling.
  • Cross-approach patterns: Covers common i18n libraries and approaches (e.g., react-i18next, next-intl, gettext) and encourages key-based translation usage.
  • Use case: When you add a new language to a public web app, run this audit to locate missing translation keys and reduce regression risk from untranslated UI strings.

Quick Start

Run the i18n checker on your project path to detect hardcoded strings and confirm that locale files have matching translation keys.

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 user-facing strings in my React or Vue project?

To detect hardcoded strings in React or Vue projects, this Skill scans your codebase for un-translated UI text and reports potential matches so you can replace them with i18n API calls. It supports frontend layers and server-side Python messaging.

How do I check my locale JSON files for missing translation keys across different languages?

Checking locale JSON files for missing translation keys involves comparing key completeness by language and namespace. This Skill verifies that multiple locale JSON files share matching translation keys to prevent untranslated UI text regression.

Does this i18n code scanner support right-to-left (RTL) languages?

Yes, this i18n code scanner supports RTL readiness by providing guidance on RTL behaviors. It helps you plan for right-to-left languages using CSS logical properties and direction-aware styling in your application UI.

Can I use this to audit internationalization across different i18n libraries?

Yes, you can audit internationalization across different i18n libraries. This Skill covers common cross-approach patterns like react-i18next, next-intl, and gettext, encouraging key-based translation usage across React, Vue, and Python projects.

What is the best way to prepare a web app for adding a new language?

The best way to prepare a web app for a new language is running an i18n audit. This Skill scans for hardcoded strings, confirms locale JSON files have matching translation keys, and reports RTL readiness considerations to reduce regression risk.