Agent skill · software engineering · aiskillstore
i18n-automation
Automate internationalization and localization workflows for web applications with translation, key generation, and library setup
Why this skill is useful
Adds specific automation scripts and configuration patterns for internationalization workflows that the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. About 6k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
i18n Automation Purpose Automate complete internationalization workflows including translation, key-value generation, library installation, and locale configuration for web applications. Specialist Agent I am an internationalization specialist with expertise in: i18n library selection and configuration (react-i18n, next-intl, i18next) Translation key architecture and organization Locale file formats (JSON, YAML, PO, XLIFF) RTL (Right-to-Left) language support SEO and metadata localization Dynamic content translation strategies Methodology (Plan-and-Solve Pattern) 1. Analyze Project: Detect framework, existing i18n setup, content to translate 2. Design i18n Architecture: Choose library, key structure, file organization 3. Extract Content: Identify all translatable strings and create keys 4. Generate Translations: Create locale files with translations 5. Configure Integration: Set up routing, language detection, switcher component 6. Validate: Test all locales, check RTL, verify SEO metadata Framework Support Next.js (Recommended: next-intl): React (Recommended: react-i18next): Vue (Recommended: vue-i18n): Translation Key Architecture Namespace Organization: Flat vs Nested Keys: Translation Strategies Strategy 1: Professional Translation Extract keys to XLIFF or JSON Send to translation service (Locize, Crowdin, Phrase) Import translated files High quality, costs money Strategy 2: AI Translation (Good for MVP) Use Claude/GPT to translate Review by native speaker recommended Fast and cost-effective May miss cultural nuances Strategy 3: Community Translation Open source projects Contributor PRs with translations Review process for quality Builds community engagement Strategy 4: Hybrid AI for initial translation Professional review for key pages Community contributions for edge cases Best balance of speed/quality/cost Language-Specific Considerations Japanese (ja): Spanish (es): Arabic (ar) - RTL: German (de): SEO and Metadata Localization Next.js Metadata: Sitemap Local …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/i18n-automation