i18n-localization
This skill teaches you how to build multilingual applications by establishing translation infrastructure, identifying hardcoded text that should be externalized, and ensuring proper locale handling across different regions and writing systems. Learn patterns for React, Next.js, and Python, plus techniques for RTL languages and locale-aware date and number formatting.
i18n-localization helps you add multi-language support to your app with translation management and RTL handling.
AI-generated summary based on this skill's SKILL.md
Install
vudovn/ag-kit/i18n-localization · repository language: TypeScript
git clone https://github.com/vudovn/ag-kit
cp -r ag-kit/.agents/skills/i18n-localization ~/.claude/skills/i18n-localizationFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I internationalize my app with i18n-localization?
i18n-localization teaches you to build multilingual applications by establishing translation infrastructure and externalizing hardcoded text. Start by organizing translation files by language, set up a localization library (React-i18next, next-intl, or gettext for Python), and implement locale-aware formatting for dates and numbers. The skill covers patterns for major frameworks and ensures your app handles multiple regions and writing systems properly.
What's the best way to detect hardcoded strings in code?
i18n-localization covers detection techniques to identify hardcoded strings that should be externalized into translation files. Use static analysis tools and code scanning to find UI text, error messages, and labels embedded directly in your source. The skill teaches you systematic approaches to audit your codebase before implementing localization, ensuring no translatable content is missed during the migration to i18n.
How can i18n-localization help with RTL support?
i18n-localization includes guidance on adding right-to-left language support for Arabic, Hebrew, and other RTL languages. Learn CSS techniques for layout mirroring, text direction handling, and UI component adjustments needed for RTL contexts. The skill covers both styling approaches and framework-specific patterns to ensure your application displays correctly across all writing systems.
How should I organize translation files across languages?
i18n-localization teaches translation file structure and management strategies for multiple languages. Learn about namespacing conventions, locale fallback configuration, and best practices for organizing keys hierarchically. The skill covers how to structure files for scalability, implement locale-specific overrides, and handle missing translations gracefully to maintain consistency across your multilingual codebase.
Does i18n-localization cover date and number formatting?
Yes, i18n-localization includes techniques for formatting dates and numbers according to locale standards. Learn how to apply locale-specific formatting rules so dates, times, currencies, and decimal separators display correctly for each region. The skill teaches both framework-built-in solutions and manual formatting approaches to ensure your application respects user locale preferences.
What frameworks and tools does i18n-localization cover?
i18n-localization teaches patterns for React (react-i18next), Next.js (next-intl), and Python (gettext). Learn setup procedures, configuration best practices, and implementation patterns specific to each framework. The skill also covers translation key management, pluralization handling, ICU message format for complex strings, and locale configuration—providing a comprehensive checklist before shipping your multilingual application.
SKILL.md
rendered from the published skill — quoted content, verbatim
i18n & Localization
> Internationalization (i18n) and Localization (L10n) best practices.
1. Core Concepts
| Term | Meaning |
|---|---|
| i18n | Internationalization - making app translatable |
| L10n | Localization - actual translations |
| Locale | Language + Region (en-US, tr-TR) |
| RTL | Right-to-left languages (Arabic, Hebrew) |
2. When to Use i18n
| Project Type | i18n Needed? |
|---|---|
| Public web app | ✅ Yes |
| SaaS product | ✅ Yes |
| Internal tool | ⚠️ Maybe |
| Single-region app | ⚠️ Consider future |
| Personal project | ❌ Optional |
3. Implementation Patterns
React (react-i18next)
import { useTranslation } from 'react-i18next';
function Welcome() {
const { t } = useTranslation();
return <h1>{t('welcome.title')}</h1>;
}
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 2 files
.agents/skills/i18n-localization/SKILL.md
.agents/skills/i18n-localization/scripts/i18n_checker.py