i18n-localization

Detect hardcoded strings and generate locale files with translation keys.

2|Updated Oct 12, 2025
One-click install
npx skills add https://github.com/haotool/app --skill i18n-localization-haotool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-localization
Source: https://github.com/haotool/app/tree/main/.agents/skills/i18n-localization
Command: npx skills add https://github.com/haotool/app --skill i18n-localization-haotool

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It helps teams identify hardcoded strings and missing translations, enabling consistent localization across products.

Core Features & Use Cases

  • Detect hardcoded strings that bypass translation systems.
  • Generate or validate locale structures (locales/en, locales/es, etc.) and ensure fallback strategies.
  • RTL support checks and guidance for right-to-left layouts across languages.

Quick Start

Scan a codebase to detect hardcoded strings and generate a baseline locales directory with 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 detect hardcoded strings in my codebase for i18n localization?

Scan your codebase to detect hardcoded strings by identifying non-translatable literals that bypass translation systems. This process flags missing translations and generates a baseline locales directory with translation keys for consistent multilingual app support.

What is the best way to generate and validate locale files for multilingual apps?

Generate and validate locale files by enforcing a structured folder structure (locales/en, locales/es) with safe fallback strategies. This ensures translation keys are correctly used and missing translations are flagged across your multilingual app.

How do I add RTL support checks for right-to-left layouts in my app?

Add RTL support by applying checks and guidance for right-to-left layouts across languages. This identifies layout issues in your codebase and ensures your localization strategy handles both LTR and RTL text directions correctly.

Does this localization audit work with mobile and server-side projects?

Yes, this localization audit applies to web, mobile, and server-side projects. It detects hardcoded strings and implements locale folder structure guidelines uniformly across different platforms to manage multilingual translations.

What are safe fallback strategies for missing translations in locale files?

Safe fallback strategies for missing translations ensure your app defaults to a primary language locale file when specific translation keys are absent. This prevents runtime errors and maintains UI consistency by validating locale structures during the audit.