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

★ 1,262 ⁮ 154 MIT updated 2026-05-10 by d-kimuson

Install

d-kimuson/claude-code-viewer/i18n · repository language: TypeScript

Manual (git clone) CLI (skillfed)

git clone https://github.com/d-kimuson/claude-code-viewer
cp -r claude-code-viewer/.claude/skills/i18n ~/.claude/skills/i18n

npx skillfed install d-kimuson/claude-code-viewer/i18n

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.json only; do not edit compiled outputs by hand.
Use ./scripts/put-transtation.js to safely update a specific entry without loading the full file into context.

Verification

Run pnpm lingui:extract when new messages are added.
Run pnpm lingui:compile to regenerate compiled catalogs.
Run scripts/lingui-check.sh to verify no missing translations.
Run scripts/i18n-check-key-equals-translation.sh to ensure key != translation in all locales.

Read as markdown · JSON record · Browse the source repository

File tree — 1 file

.claude/skills/i18n/SKILL.md

All skills by d-kimuson →