resume-i18n-translate
Extract i18n keys and translate the resume app locales using the existing OpenRouter-based scripts. Use when updating translation keys, adding languages, or re-running translations for dev/apps/resume and its i18next locale files.
When & Why to Use This Skill
This Claude skill automates the internationalization (i18n) and localization workflow for the resume application. It streamlines the end-to-end process of extracting i18next keys from the codebase and generating high-quality translations via OpenRouter-powered scripts, ensuring the application remains synchronized across multiple languages with minimal manual intervention.
Use Cases
- Automated Key Extraction: Automatically scan the source code to identify and extract new or modified i18n keys, ensuring locale files are always up-to-date with the latest UI changes.
- Multi-language Expansion: Rapidly add support for new languages by leveraging AI-driven scripts to translate the entire application's string library in one workflow.
- Continuous Localization Maintenance: Efficiently re-run and audit translations for the resume app to maintain consistency and accuracy across all supported locales after major content updates.
| name | resume-i18n-translate |
|---|---|
| description | Extract i18n keys and translate the resume app locales using the existing OpenRouter-based scripts. Use when updating translation keys, adding languages, or re-running translations for dev/apps/resume and its i18next locale files. |
Resume I18n Translate
Overview
Extract i18next keys and regenerate locale files for the resume app using the repository translation prompt and scripts.
Workflow
- Review the translation prompt and locale layout in
dev/apps/resume/scripts/translation/prompt.mdanddev/apps/resume/src/i18n/locales. - Extract keys:
cd dev/apps/resume && pnpm i18n:extract. - Translate:
OPENROUTER_API_KEY=... pnpm i18n:translate. - Inspect updated locale files for accuracy and avoid introducing new facts beyond the source content.