i18n
Internationalization (i18n) workflow and standards for managing translations. Use when: (1) Adding new user-facing text, (2) Creating new components with user-facing text, (3) Reviewing code for i18n compliance, (4) Adding a new translation module.
npx skills add iOfficeAI/AionUi --skill i18n --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# i18n Skill Standards and workflow for internationalization. All user-visible text must use i18n. **Announce at start:** "I'm using i18n skill to ensure proper internationalization." ## IMPORTANT: Read Config First Before doing any i18n work, **always read `src/common/config/i18n-config.json`** to get the current list of supported languages and modules. Never assume a fixed number — languages and modules may have been added or removed since this skill was written. ```bash cat src/common/config/i18n-config.json ``` This file is the **single source of truth**. All scripts, runtime code, and this workflow depend on it. ## File Structure ``` src/common/config/i18n-config.json # Single source of truth: languages, modules src/renderer/i18n/ ├── index.ts # i18next configuration ├── i18n-keys.d.ts # AUTO-GENERATED — do not edit manually └── locales/ ├── <lang>/ # One directory per language in i18n-config.json │ ├── index.ts # Barrel import for all modules │ ├── common.json # One JSON per module in i18n-config.json │ ├── conversation.json │ └── ... └── ... ``` ### Key Facts - **Reference language**: defined by `referenceLanguage` in `i18n-config.json` (currently `en-US`) - **Supported lang
- IMPORTANT: Read Config First
- File Structure
- Key Facts
- Key Structure
- Key Naming Rules
- Common Suffixes
- Adding New Text — Workflow
- Step 1: Read src/common/config/i18n-config.json
- Step 2: Check Existing Keys
- Step 3: Choose the Right Module
- Step 4: Add to ALL Locale Directories
- Step 5: Use in Component
- Step 6: Regenerate Types and Validate
- Adding a New Module
cat src/common/config/i18n-config.json grep -r "keyword" src/renderer/i18n/locales/en-US/ bun run i18n:types # Step A: regenerate i18n-keys.d.ts from reference locale node scripts/check-i18n.js # Step B: validate structure, keys, and type sync
What does the i18n skill do?
Internationalization (i18n) workflow and standards for managing translations. Use when: (1) Adding new user-facing text, (2) Creating new components with user-facing text, (3) Reviewing code for i18n compliance, (4) Adding a new translation module.
How do I install it?
Run `npx skills add iOfficeAI/AionUi --skill i18n --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From iOfficeAI/AionUi, a repository with 31,403 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.