Tags
Best Internationalization Skills for AI Agents
40 Internationalization skills for AI coding assistants — ranked by popularity.
Developing software for a global audience requires handling fragmented locale requirements, language-specific formatting, and platform-native standards. This collection provides curated AI-agent skills designed to automate and enforce internationalization best practices across different technology stacks. Whether you are managing react-i18next keys for a web application, handling .xcstrings for iOS, or configuring font support for PDF generation, these SKILL.md files equip your AI assistant with the necessary context to avoid common localization pitfalls. These tools are built for developers who need to shift from manual string extraction and translation management to automated, context-aware workflows. By integrating these skills, you ensure that your codebase maintains consistent locale handling, correct RTL support, and adherence to extension-specific guidelines. You can expect your AI agent to better detect hardcoded strings, suggest appropriate translation patterns, and navigate complex directory structures with ease. Stop guessing about localization standards and use these targeted expert definitions to manage your global project requirements accurately.
Top Internationalization skills
i18n-localization
davila7
Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.
browser-extension-developer
yamadashy
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
i18n
lobehub
Internationalization guide using react-i18next. Use when adding translations, creating i18n keys, or working with localized text in React components (.tsx files). Triggers on translation tasks, locale management, or i18n implementation.
vscode-ext-localization
github
Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices
localization-developer
anyproto
Context-aware routing to the Anytype iOS localization system. Use when working with .xcstrings files, Loc constants, hardcoded strings, or user-facing text.
i18n-expert
daymade
This skill should be used when setting up, auditing, or enforcing internationalization/localization in UI codebases (React/TS, i18next or similar, JSON locales), including installing/configuring the i18n framework, replacing hard-coded strings, ensuring en-US/zh-CN coverage, mapping error codes to localized messages, and validating key parity, pluralization, and formatting.
lokalise-core-workflow-b
jeremylongshore
Execute Lokalise secondary workflow: Download translations and integrate with app. Use when downloading translation files, exporting translations, or integrating Lokalise output into your application. Trigger with phrases like "lokalise download", "lokalise pull translations", "export lokalise", "get translations from lokalise".
1k-i18n
OneKeyHQ
Internationalization — translations (ETranslations, useIntl, formatMessage) and locale management. NEVER modify auto-generated translation files.
lokalise-data-handling
jeremylongshore
Implement Lokalise translation data handling, PII management, and compliance patterns. Use when handling sensitive translation data, implementing data redaction, or ensuring compliance with privacy regulations for Lokalise integrations. Trigger with phrases like "lokalise data", "lokalise PII", "lokalise GDPR", "lokalise data retention", "lokalise privacy", "lokalise compliance".
lokalise-hello-world
jeremylongshore
Create a minimal working Lokalise example. Use when starting a new Lokalise integration, testing your setup, or learning basic Lokalise API patterns. Trigger with phrases like "lokalise hello world", "lokalise example", "lokalise quick start", "simple lokalise code".
translations
mikopbx
Управление многоязычными переводами на 29 языков с приоритетом русского языка. Использовать при добавлении новых переводов, переводе на все языки, проверке консистентности или удалении устаревших ключей.
generate-translations
payloadcms
Use when new translation keys are added to packages to generate new translations strings
lokalise-core-workflow-a
jeremylongshore
Execute Lokalise primary workflow: Upload source files and manage translation keys. Use when uploading translation files, creating/updating keys, or managing source strings in Lokalise projects. Trigger with phrases like "lokalise upload", "lokalise push keys", "lokalise source strings", "add translations to lokalise".
localize
ryokun6
Localize ryOS apps and components by extracting hardcoded strings, replacing with translation keys, and syncing across languages. Use when localizing an app, adding i18n support, translating UI text, or working with translation files.
restapi-translations
mikopbx
Управление переводами REST API ключей (rest_*) для MikoPBX. Автоматически находит отсутствующие русские ключи в RestApi.php и синхронизирует их с исходным кодом. Использовать при проверке переводов API, после добавления новых endpoints или перед релизом.
freshrss-i18n
FreshRSS
Add, move, or format translation strings in FreshRSS. Use when modifying UI text that needs translation (i18n). Handles all supported languages automatically.
intl-expansion
alirezarezvani
International market expansion strategy. Market selection, entry modes, localization, regulatory compliance, and go-to-market by region. Use when expanding to new countries, evaluating international markets, planning localization, or building regional teams.
i18n-localization
Harmitx7
Internationalization (i18n) and localization mastery. Abstracting hardcoded strings, managing JSON/YAML translation dictionaries, bidirectional routing (RTL support for Arabic/Hebrew), Pluralization algorithms, date/currency formatting, and SSR locale detection in Next.js/React. Use when preparing a
frontend-system
ZroZoom
UI/UX expert. Use for creating components, styling (Tailwind), accessibility, and translations (I18n). Trigger when: create a component, change appearance, add a chart, translate, stwórz komponent, zmień wygląd, dodaj wykres, przetłumacz.
review-frontend
OpenAEV-Platform
>-
add-i18n-locale
GXFG
NaiveTab 浏览器扩展的 i18n 国际化开发指南。当用户要新增/修改翻译文本、添加多语言 key 时使用。涵盖中英文同步更新规则、变量替换模式等,防止遗漏或格式错误。
qudjp-localization-triage
ToaruPen
Use when working in QudJP on untranslated or incorrectly translated Caves of Qud runtime text, player.log triage, owner-route vs sink-route decisions, generated/composed names, HistorySpice text, dictionary leaf additions, or localization patches that need decompiled producer tracing and focused ver
i18n-check
FriendlyInternet
Pre-commit i18n check. Scans changed files for untranslated strings, missing locale keys, and locale sync issues. Fast and focused — only checks what changed. Use before committing or as a review add-on.
React + Ant Design Frontend
daithang-organization
Complete guide for the SE104_VLEAGUE React frontend — pages, services, components, auth flow, i18n, and patterns
How to choose a Internationalization skill
Start by identifying your specific technology stack and output target. If you are building a React application, prioritize skills like i18n-localization or lobehub's i18n for their focus on component-level translation. If you work within specialized environments like VS Code or Anytype, select the corresponding platform-specific skills. Evaluate each skill based on how well it maps to your file structure and whether it addresses the specific formatting needs of your target languages, such as Chinese font support in PDFs or RTL layout requirements. Always check the repository maintenance frequency to ensure the guidelines align with current library versions.