i18n
Manage translations across multiple locales in Lingui catalogs without altering source keys or compiled outputs. The skill enforces preservation of placeholders, ICU syntax, and technical terminology while providing verification scripts to catch missing translations and ensure consistency.
i18n helps you update or fix translations in Lingui catalogs safely.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-05-10
i18n helps you update or fix translations in Lingui catalogs safely. Manage translations across multiple locales in Lingui catalogs without altering source keys or compiled outputs. The skill enforces preservation of placeholders, ICU syntax, and technical terminology while providing verification scripts to catch missing translations and ensure consistency.
Use it when
- i18n provides workflows for managing multilingual messages across your application's locales.
- i18n includes verification scripts that catch missing translations and validate completeness across your locales.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
d-kimuson/claude-code-viewer/i18n · repository language: TypeScript
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I update lingui catalogs safely?
i18n helps you update Lingui catalogs while preserving source keys, placeholders, and ICU syntax. The skill manages translation updates across locales without altering compiled outputs, ensuring your message structure stays intact. Use i18n's verification scripts to validate changes before deployment.
What does i18n do for managing i18n translations?
i18n provides workflows for managing multilingual messages across your application's locales. It handles catalog maintenance, locale file updates, and ensures technical terminology and formatting rules are preserved. The skill lets you update translation keys and manage message files consistently across all supported languages.
How can I fix missing translations in my Lingui setup?
i18n includes verification scripts that catch missing translations and validate completeness across your locales. Run these scripts to identify gaps in your translation coverage, then use i18n's catalog management tools to add translations systematically and ensure no messages are left untranslated.
Can i18n extract and compile internationalization catalogs?
Yes, i18n supports extracting and compiling internationalization catalogs as part of its translation workflow. The skill handles catalog extraction from your source code and compilation into optimized message files, maintaining consistency with your i18n message structure throughout the process.
What's the best way to validate translation completeness?
i18n provides translation verification scripts designed to validate completeness across all locales. These tools check for missing translations, verify placeholder consistency, and ensure ICU syntax is correct. Run validation before updates to catch issues early and maintain quality across your multilingual application.
Does i18n preserve placeholders and ICU syntax?
i18n is built to enforce preservation of placeholders, ICU syntax, and technical terminology in your Lingui catalogs. When you update translations, the skill maintains these critical elements unchanged, preventing formatting errors and ensuring your internationalized messages render correctly across all locales.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Core rules
- English (
en) is the source catalog. Do not alter keys; only update translations. - Preserve placeholders and ICU syntax exactly (e.g.,
{name},{count, plural, one {...} other {...}}). - Keep technical terms in English when appropriate (API, TypeScript, React).
Translation updates
- Update
src/lib/i18n/locales/{locale}/messages.jsononly; do not edit compiled outputs by hand. - Use
./scripts/put-transtation.jsto safely update a specific entry without loading the full file into context.
Verification
- Run
pnpm lingui:extractwhen new messages are added. - Run
pnpm lingui:compileto regenerate compiled catalogs. - Run
scripts/lingui-check.shto verify no missing translations. - Run
scripts/i18n-check-key-equals-translation.shto ensure key != translation in all locales.
File tree — 1 file
.claude/skills/i18n/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Update or fix translations in Lingui catalogs”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Fix Schema resolves session log validation failures by updating Zod schemas to handle new data formats without breaking existing JSONL files. It guides you through locating the relevant schema, updating type definitions, adding tests, and creating a pull request with all changes verified.
This skill orchestrates the complete release process for claude-code-viewer, from version specification through signed commit creation, tag management, and GitHub Actions workflow monitoring. It handles version bumps (patch, minor, major, beta, or explicit semver), validates preconditions like SSH signing config, and guides you through GitHub Release note cleanup and publishing.
This skill covers implementing internationalization in React and vanilla JavaScript applications using Lingui. You'll learn the standard workflow—marking messages with macros, extracting and translating catalogs, then compiling and activating locales—plus patterns for pluralization, date/number formatting, and dynamic locale switching. Best practices include choosing the right macro for your context and leveraging the ESLint plugin to catch common mistakes.
Software Localisation guides you through implementing internationalisation and localisation across modern web frameworks. It covers library selection (react-i18next, react-intl, vue-i18n, @angular/localize, next-intl), ICU message formatting, character encoding standards, and CI/CD workflows to prevent mixed-language regressions.
This skill walks you through converting an i18next-based project to Lingui, from installing dependencies and configuring build tools through rewriting React components and translation strings. It addresses namespace mapping, plural form restructuring, and catalog format changes, then shows how to extract and compile your messages for production.
Translate replaces expensive full-model translation runs by extracting empty msgstr entries from Lingui catalogs, chunking them, and dispatching Haiku subagents to translate each batch. Results merge back deterministically into your locale files with zero model overhead in the write path. Use this when you need to fill missing translations after adding new UI strings.
More skills Localization Engineer (unlicensed)