i18n-localization

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

Updated Sep 2, 2025
One-click install
npx skills add https://github.com/rafaelminatto1/fisioflow-51658291 --skill i18n-localization-rafaelminatto1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-localization
Source: https://github.com/rafaelminatto1/fisioflow-51658291/tree/main/.agent/skills/i18n-localization
Command: npx skills add https://github.com/rafaelminatto1/fisioflow-51658291 --skill i18n-localization-rafaelminatto1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Internationalization and Localization best practices: Detecting hardcoded strings, managing translations, locale files, and RTL support across projects.

Core Features & Use Cases

  • Patterns and guidance for React (react-i18next), Next.js (next-intl), and Python gettext implementations.
  • Locale structure guidance, best practices for translation keys, pluralization, and RTL handling.
  • Code quality and auditing with the i18n_checker.py script to detect hardcoded strings and missing translations, and to verify locale completeness.

Quick Start

Run the i18n_checker.py script on your project to identify 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 my React or Next.js codebase?

You can find hardcoded strings in React and Next.js projects by running the i18n_checker.py script. It audits your source code to detect unlocalized text and verifies locale completeness against your translation files.

What is the best way to check for missing translations and locale parity?

The best way to check for missing translations is to run the i18n_checker script across your project. It identifies structural inconsistencies, detects missing keys in locale files, and enforces locale parity for your web applications.

Does this i18n localization approach work with Vue and Python projects?

Yes, this i18n localization approach works with Vue and Python projects. It provides patterns and guidance for Python gettext implementations alongside React, Next.js, and locale file management to ensure consistent translation practices.

How do I handle RTL support and pluralization when managing locale files?

To handle RTL support and pluralization, apply the provided i18n locale structure guidance. It enforces best practices for translation keys and RTL handling to maintain structural consistency across all localized web applications.

Why are my i18n translation keys showing structural inconsistencies?

i18n translation keys show structural inconsistencies when locale files lack parity or contain missing keys. Running the i18n_checker script detects these mismatches and enforces proper internationalization patterns across your codebase.