i18n Workflow
Standardized internationalization workflow for AionUi, ensuring all user-visible text is properly translated.
The skill is purely documentation describing an i18n workflow; no malicious behavior or overreach found. However, it lacks permission isolation, confirmation mechanisms, and data-flow transparency, and the publisher is unverified, so deductions apply.
The document is internally consistent and provides clear commands and steps, but lacks evidence of actual test coverage, error-handling details are shallow, and static review cannot verify key-path reproducibility.
The skill targets a clear i18n workflow, but it does not declare capability boundaries or precise trigger conditions, risking mis-invocation. It also relies on repo-specific structure and does not consider Chinese-user environment fit (e.g., network reachability).
The document is well-structured with checklists and common-mistakes tables, but lacks versioning, changelog, known limitations, and explicit ownership.
The document can guide i18n tasks, but direct usability of outputs is unverified and there is limited evidence of comparative benefit over alternatives.
Beyond test commands in README and CI workflows, there is no independent verification or third-party execution evidence; static review cannot confirm key claims.
- The skill is documentation-only but does not declare permission boundaries or data flow; follow least-privilege principles during execution.
- The repo relies on GitHub Actions and OpenAI API, which may be unreachable from mainland China; consider network adaptation if the skill depends on these services.
- The skill description is based on the current repo state but lacks version compatibility notes and may become outdated as the repo evolves.
What does this skill do, and when should you use it?
This skill defines a comprehensive internationalization (i18n) workflow for the AionUi codebase. It provides guidelines for adding new user-facing text, creating components, reviewing code for i18n compliance, and introducing new translation modules. The skill emphasizes reading `src/common/config/i18n-config.json` as the single source of truth for supported languages and modules, and mandates adding every new key to all locales. It includes type generation and validation scripts to ensure consistency, and prohibits hardcoded strings in JSX. It is part of a monorepo with other skills, but this profile focuses solely on the i18n skill.
The skill performs the following concrete operations: reads the config file src/common/config/i18n-config.json to get the current language and module lists; manages translation JSON files under src/renderer/i18n/locales/<lang>/; enforces namespaced dot-notation keys like t('module.key'); when adding new text, requires adding keys to every locale directory; runs bun run i18n:types to regenerate type definitions (i18n-keys.d.ts); runs node scripts/check-i18n.js to validate structure, key sync, and type alignment; and detects and prevents hardcoded Chinese/English text in JSX by checking prohibited patterns.
- A developer adding a new UI feature needs to ensure all user-visible strings are translated across all supported languages.
- A developer creating a new component with user-facing text must follow the skill's workflow to add proper i18n keys instead of hardcoding strings.
- A code reviewer checks a pull request for i18n compliance, looking for hardcoded strings and verifying all keys are added to all locales.
- A developer needs to add a completely new translation module (e.g., `cron`) and must follow the multi-step process to register it in the config and all locale files.
What are this skill's strengths and limitations?
- Provides a clear, repeatable workflow ensuring all locales stay in sync.
- Auto-generates TypeScript type definitions, reducing manual errors.
- Includes hardcoded string detection to enforce best practices.
- Config-driven makes adding languages/modules straightforward.
- Tied to AionUi's specific project structure; not a generic i18n solution.
- Requires specific tooling (Bun, Node.js) and custom scripts.
- Lacks automated translation quality checks; relies on human review.
- Documentation does not cover reusing this skill outside the AionUi codebase.
How do you install this skill?
This skill is part of the AionUi repository, located at .claude/skills/i18n/. To use it, clone the entire repository or copy the skill folder into your Claude Code skills directory. Ensure you have Bun and Node.js installed, as the validation scripts rely on them.
How do you use this skill?
When working on code that includes user-visible text, invoke this skill by referencing it in your prompt. The skill's workflow will guide you: start by reading src/common/config/i18n-config.json to know the current languages and modules. Then add new keys to every locale's corresponding module file, use t() in components, and finally run bun run i18n:types and node scripts/check-i18n.js to validate. For example, you might say: 'I'm using the i18n skill to add a new translation key.'