i18n-localization

Name: i18n-localization
Availability: InStock
Author: r2w1cs

Detect hardcoded strings and missing translations in application codebases.

1|Updated Mar 14, 2026

Search Tags:#localization #i18n #internationalization #RTL #L10n

Ready to run

npx skills add https://github.com/R2W1cs/Mustacademy --skill i18n-localization-r2w1cs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: i18n-localization
Source: https://github.com/R2W1cs/Mustacademy/tree/main/a/.agent/skills/i18n-localization
Command: npx skills add https://github.com/R2W1cs/Mustacademy --skill i18n-localization-r2w1cs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of implementing proper internationalization (i18n) and localization (L10n) in your applications, ensuring your software supports multiple languages and right-to-left (RTL) text.

Core Features & Use Cases

Internationalization and Localization Patterns: Identifies hardcoded strings, manages translations, and implements locale-specific files and RTL support.
Best Practices: Offers guidelines on how to structure translation files, handle pluralization, and format dates and numbers according to locale.
Common Issues: Identifies missing translations, hardcoded strings, and improper formatting.
RTL Support: Ensures that the layout and design of the app are suitable for right-to-left languages.
Checklist: Provides a checklist for verifying that all user-facing strings are translated, locale files are complete, and RTL layouts are tested.

Quick Start

Use the i18n-localization skill to check the i18n status of your project.

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 and missing translations in my codebase?▼

Automating i18n and localization detection scans your codebase using regex and path manipulation to identify hardcoded strings, missing translations, and improper formatting across application files.

What is the best way to ensure my application supports right-to-left (RTL) languages?▼

RTL support assessment evaluates your application's layout and design suitability for right-to-left languages, ensuring proper internationalization patterns and locale-specific file management are implemented.

How do I structure translation files and handle locale-specific pluralization?▼

Proper localization practices structure translation files in JSON format, managing pluralization and formatting dates and numbers according to specific locale requirements for complete coverage.

Can I check my project's internationalization status without external dependencies?▼

Yes, this i18n analysis operates with no external dependencies, using regex, JSON, and path manipulation to assess your codebase structure and content for localization completeness.

Why does my application have missing translations and improper locale formatting?▼

Missing translations and improper formatting occur when hardcoded strings bypass localization files, requiring a comprehensive checklist to verify all user-facing strings are translated and locale files are complete.

What should be on my localization verification checklist before release?▼

A complete localization checklist verifies all user-facing strings are translated, locale files are fully populated, and RTL layouts are tested to ensure proper internationalization support.