i18n

Detect hardcoded strings and manage JSON translation files for internationalization.

7|2|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/LuisSambrano/antigravity-config --skill i18n-luissambrano
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n
Source: https://github.com/LuisSambrano/antigravity-config/tree/main/skills/3-web/i18n
Command: npx skills add https://github.com/LuisSambrano/antigravity-config --skill i18n-luissambrano

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of making applications accessible to a global audience by managing internationalization (i18n) and localization (L10n), preventing hardcoded strings, and ensuring proper handling of different languages and regional formats.

Core Features & Use Cases

  • Detects Hardcoded Strings: Identifies untranslated text directly embedded in code.
  • Manages Translation Files: Organizes locale data in structured formats (e.g., JSON).
  • Supports RTL Languages: Provides guidance on implementing Right-to-Left text direction.
  • Use Case: Ensure your web application can be seamlessly translated into Spanish, French, and Arabic, maintaining correct text direction and formatting for each locale.

Quick Start

Run the i18n checker script to audit the project for hardcoded strings and locale completeness.

Frequently Asked Questions about i18n

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect hardcoded strings in my web application for internationalization?

To manage translation files for localization, organize your locale data in structured formats like JSON. This ensures your web application can be seamlessly translated into multiple languages while maintaining correct formatting.

What is the best way to support RTL layouts for languages like Arabic?

The best way to support RTL layouts is by implementing Right-to-Left text direction guidance. This ensures proper handling of different languages and regional formats for seamless global deployment of your SaaS products.

How do I manage translation files for multi-language localization in a SaaS product?

To manage translation files for localization, organize your locale data in structured JSON formats. This approach prevents hardcoded strings and ensures proper handling of different languages and regional formats across your SaaS product.

Does this internationalization approach work for both web applications and SaaS products?

Yes, this internationalization approach works for web applications, SaaS products, and any software requiring multi-language support. It applies i18n patterns and best practices to ensure proper handling of different languages and regional formats.

Why does my app show untranslated text after setting up locale files?

Your app shows untranslated text because hardcoded strings are embedded directly in the code. Run the i18n checker script to audit the project, identify these untranslated strings, and ensure locale completeness.