i18n-localization

Identify hardcoded strings and manage locale translation files.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/simoabid/ABID.Dev-Portfolio --skill i18n-localization-simoabid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-localization
Source: https://github.com/simoabid/ABID.Dev-Portfolio/tree/main/.agent/skills/i18n-localization
Command: npx skills add https://github.com/simoabid/ABID.Dev-Portfolio --skill i18n-localization-simoabid

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 providing patterns and tools for internationalization (i18n) and localization (L10n), ensuring consistent and culturally appropriate user experiences across different languages and regions.

Core Features & Use Cases

  • Detecting Hardcoded Strings: Identifies and flags text directly embedded in the code that should be externalized for translation.
  • Managing Translations: Offers guidance on structuring and maintaining locale files (e.g., JSON) for different languages.
  • Locale File Management: Provides a clear file structure for organizing translations by language and feature.
  • RTL Support: Includes CSS best practices for right-to-left language layouts.
  • Use Case: A web application needs to be translated into Spanish, French, and Arabic. This Skill helps ensure all user-facing text is properly marked for translation, locale files are created, and the UI adapts correctly for RTL languages like Arabic.

Quick Start

Run the i18n checker script against your project directory to identify potential issues.

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 codebase for translation?

Run an i18n checker script against your project directory to identify hardcoded strings for translation. This script scans your codebase to flag text directly embedded in the code that should be externalized into locale files.

What is the best way to structure locale files for multiple languages?

The best way to structure locale files is to organize translations by language and feature within JSON files. This provides a clear file structure for maintaining locale-specific adaptations and ensuring consistent user experiences across regions.

Does this approach support right-to-left (RTL) layouts for Arabic?

Yes, this approach supports right-to-left (RTL) layouts for languages like Arabic. It includes CSS best practices to ensure your UI adapts correctly for RTL languages, making your application culturally relevant for a global user base.

When do I need internationalization patterns for my web application?

You need internationalization patterns when your web application must be accessible to a global audience. These patterns help ensure all user-facing text is properly marked for translation and the UI adapts to locale-specific cultural requirements.

Can I use this to manage translations across Spanish, French, and Arabic?

Yes, you can use this to manage translations across Spanish, French, and Arabic. It guides developers on structuring and maintaining locale files, creating a clear file structure for organizing translations by language and feature.