i18n-localization

Extract hardcoded strings and organize translation catalogs for software localization.

1|Updated Jun 23, 2026
One-click install
npx skills add https://github.com/phuonghx/aim-cli --skill i18n-localization-phuonghx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-localization
Source: https://github.com/phuonghx/aim-cli/tree/main/aim/templates/aim-agents/skills/i18n-localization
Command: npx skills add https://github.com/phuonghx/aim-cli --skill i18n-localization-phuonghx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gettext, icu, Intl, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenges of making an app translatable and adapting it to different locales, including handling hardcoded strings, organizing translation catalogs, and supporting right-to-left layouts.

Core Features & Use Cases

  • Internationalization (i18n): Facilitates building an app that can be translated without baked-in text, with locale-aware formatting and layouts that adjust.
  • Localization (l10n): Manages the actual translations and regional conventions for different languages and regions.
  • Use Case: When adding multi-language support, auditing for untranslated text, structuring locale files, or wiring up right-to-left (RTL) layouts in your app.

Quick Start

Run the script to check for hardcoded strings and out-of-sync catalogs in 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 extract hardcoded strings for internationalization?

Extract hardcoded strings by running the provided script to audit your project, identifying text that needs translation and generating organized translation catalogs for localization.

What is the best way to support right-to-left layouts in my app?

Support right-to-left layouts by implementing locale-aware formatting and layout adjustments provided through internationalization practices, ensuring your app adapts its UI direction per locale.

Can I use gettext and ICU message syntax for translation catalogs?

Yes, gettext and ICU message syntax are supported for structuring translation catalogs. These libraries help manage locale-specific messages and regional conventions within your application.

Do I need Python 3.8+ to use this localization tool?

Yes, Python 3.8+ is required. The tool uses Python libraries like gettext, ICU message syntax, and Intl APIs to handle internationalization tasks such as extracting strings and formatting locales.

How do I organize translation catalogs for multi-language support?

Organize translation catalogs by auditing untranslated text and structuring locale files using supported libraries like gettext and ICU, ensuring your app can adapt to different languages and regions.

Why does my app need locale-specific formatting for internationalization?

Locale-specific formatting is needed because internationalization requires your app to adapt dates, numbers, and text conventions per region, ensuring the UI displays correctly across different locales without baked-in text.