i18n-localization

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

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/Oscar-Ivan-Salas/PILi_Quarts_Doc --skill i18n-localization-oscar-ivan-salas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-localization
Source: https://github.com/Oscar-Ivan-Salas/PILi_Quarts_Doc/tree/main/PILi_Quarts_V3.0/.agent/skills/i18n-localization
Command: npx skills add https://github.com/Oscar-Ivan-Salas/PILi_Quarts_Doc --skill i18n-localization-oscar-ivan-salas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Internationalization and localization patterns are critical to build software that works across languages; this Skill helps identify hardcoded strings, enforce translation keys, and ensure locale files and RTL support are in place.

Core Features & Use Cases

  • Detect hardcoded text in React, Vue, and Python codebases.
  • Provide concrete i18n usage patterns (e.g., react-i18next, next-intl, gettext) and guidance.
  • Validate locale files across languages for key consistency and coverage.
  • Ensure RTL support readiness and best practices for locale-specific formatting.

Quick Start

Run the i18n checker against your project to identify hardcoded strings and verify locale coverage.

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

To find hardcoded strings, this tool audits your codebase to detect internationalization gaps, identifying unassigned UI text and providing remediation guidance for missing translation keys and locale files.

What is the best way to check locale file consistency across multiple languages?

Checking locale file consistency involves validating translation keys across all language files to ensure complete coverage. This auditing process detects missing keys and enforces structural consistency for your internationalization setup.

Does this i18n checker work with Python backends and Next.js applications?

Yes, this i18n checker works with Python backends and Next.js applications. It detects hardcoded text and provides concrete usage patterns for frameworks like next-intl and gettext to enforce translation keys.

How do I ensure RTL support readiness in my application code?

Ensuring RTL support readiness requires auditing your codebase for internationalization best practices. This process checks for proper locale-specific formatting and validates that your UI components support right-to-left language layouts.

How do I add missing translation keys to my locale files?

To add missing translation keys, run an internationalization audit to identify hardcoded text. The tool generates remediation guidance, specifying exact i18n usage patterns and the required locale file updates for your translations.