localization-toolkit
This skill guides you through complete internationalization setup and auditing for modern web applications. Configure your chosen i18n framework, systematically replace user-facing strings with localization keys, ensure consistent coverage across target locales (en-US and zh-CN by default), and validate pluralization and formatting rules. The workflow covers framework selection, locale file organization, error message localization, and testing strategies.
Localization-toolkit helps you set up i18n frameworks and audit locale parity across React, Next.js, and Vue applications.
AI-generated summary based on this skill's SKILL.md
Install
zebbern/claude-code-guide/localization-toolkit · repository language: Python
git clone https://github.com/zebbern/claude-code-guide
cp -r claude-code-guide/skills/localization-toolkit ~/.claude/skills/localization-toolkitFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How to set up i18n in React with localization-toolkit?
localization-toolkit guides you through complete i18n framework configuration for React, Next.js, and Vue apps. Start by selecting your framework and initializing locale files (en-US, zh-CN, or custom locales). The toolkit helps you organize translation keys, configure fallback languages, and integrate the framework into your component tree. Follow the setup workflow to establish locale file structure and enable language switching from the start.
How do I audit localization keys in my codebase?
localization-toolkit provides auditing capabilities to identify missing translations and validate locale key parity across your app. The audit scans your codebase for hardcoded strings, detects unused translation keys, and flags mismatches between locale files. Run the audit tool to generate a report showing which keys exist in en-US but are missing from zh-CN, or vice versa, ensuring consistent coverage.
What's the best way to replace hardcoded strings with translation keys?
localization-toolkit guides systematic replacement of hardcoded UI strings with localization keys. Extract user-facing text into your locale files, then update components to reference those keys through your i18n framework's hooks or helper functions. The toolkit validates each replacement to ensure the key exists in all target locales before deployment, preventing runtime translation failures.
How does localization-toolkit handle error messages and pluralization?
localization-toolkit supports localization of error messages with context-aware formatting and pluralization rules. Define plural forms in your locale files (e.g., singular/plural variants for different languages), configure number and date formatting per locale, and use the toolkit's validation to ensure formatting rules match across en-US, zh-CN, and other target languages.
Can localization-toolkit help implement language switching in React?
localization-toolkit provides patterns for implementing language switchers and persisting locale preferences. Configure locale switching logic, store user language selection in localStorage or cookies, and ensure all components re-render with the new locale. The toolkit includes best practices for maintaining language state across page navigation and app restarts.
What does localization-toolkit include for locale file organization?
localization-toolkit recommends and validates locale file organization best practices. Structure translations by feature or page, use nested key hierarchies for clarity, and organize locale files by language code (en-US, zh-CN). The toolkit helps you maintain consistent naming conventions, validate JSON structure, and manage growing translation catalogs as your app scales.
SKILL.md
rendered from the published skill — quoted content, verbatim
I18n Expert
Overview
Deliver a complete i18n setup + audit pass: configure the i18n framework, replace user-facing strings with keys, ensure locale parity, and validate pluralization/formatting for en-US and zh-CN.
Core Capabilities
- Library selection and setup (React, Next.js, Vue).
- Key architecture and locale file organization.
- Translation generation and quality strategy (AI, professional, manual).
- Routing and language detection/switching.
- SEO and metadata localization (when applicable).
- RTL support (only if RTL locales are in scope).
Scope Inputs (ask if unclear)
- Framework and routing style.
- Existing i18n state (none, partial, legacy).
- Target locales (default: en-US + zh-CN).
- Translation quality needs (AI vs professional vs
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 4 files
skills/localization-toolkit/.security-scan-passed
skills/localization-toolkit/LICENSE
skills/localization-toolkit/SKILL.md
skills/localization-toolkit/scripts/i18n_audit.py