Agent skill

Internationalization Workflow with i18n

Standards for keeping all user-facing text translatable: read the i18n config first, use namespaced keys, reuse shared strings and follow the key naming rules.

Apache-2.0Auto-check passedFrontend & Design

Install Internationalization Workflow with i18n

skills CLI

$ npx skills add iOfficeAI/AionUi --skill i18n -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install iOfficeAI/AionUi i18n --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/iOfficeAI/AionUi.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/i18n .claude/skills/i18n && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "i18n" agent skill from https://github.com/iOfficeAI/AionUi/tree/main/.claude/skills/i18n into .claude/skills/i18n/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i18n", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/iOfficeAI/AionUi/tree/main/.claude/skills/i18n

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add iOfficeAI/AionUi --skill i18n -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install iOfficeAI/AionUi i18n --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iOfficeAI/AionUi.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/i18n .agents/skills/i18n && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "i18n" agent skill from https://github.com/iOfficeAI/AionUi/tree/main/.claude/skills/i18n into .agents/skills/i18n/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i18n", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add iOfficeAI/AionUi --skill i18n -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install iOfficeAI/AionUi i18n --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iOfficeAI/AionUi.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/i18n .cursor/skills/i18n && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "i18n" agent skill from https://github.com/iOfficeAI/AionUi/tree/main/.claude/skills/i18n into .cursor/skills/i18n/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i18n", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/iOfficeAI/AionUi.git --path .claude/skills/i18n

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add iOfficeAI/AionUi --skill i18n -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install iOfficeAI/AionUi i18n --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iOfficeAI/AionUi.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/i18n .gemini/skills/i18n && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "i18n" agent skill from https://github.com/iOfficeAI/AionUi/tree/main/.claude/skills/i18n into .gemini/skills/i18n/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i18n", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install iOfficeAI/AionUi i18n

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add iOfficeAI/AionUi --skill i18n -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/iOfficeAI/AionUi.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/i18n .github/skills/i18n && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "i18n" agent skill from https://github.com/iOfficeAI/AionUi/tree/main/.claude/skills/i18n into .github/skills/i18n/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i18n", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add iOfficeAI/AionUi --skill i18n -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install iOfficeAI/AionUi i18n --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iOfficeAI/AionUi.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/i18n .opencode/skills/i18n && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "i18n" agent skill from https://github.com/iOfficeAI/AionUi/tree/main/.claude/skills/i18n into .opencode/skills/i18n/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i18n", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: i18n
GitHub stars: 33k
Used in: 1 other repo
Token cost: ~1.9k tokens
SKILL.md length: 641 words
Files: 1
Skills in repo: 4
Repo updated: Sep 9, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Standards for keeping all user-facing text translatable: read the i18n config first, use namespaced keys, reuse shared strings and follow the key naming rules.

Works in 6 steps: Read src/common/config/i18n-config.json → Check Existing Keys → Choose the Right Module → …
Adding new user-facing text to an existing screen
SKILL.md covers IMPORTANT: Read Config First, File Structure, Key Structure and Adding New Text — Workflow, plus 6 more sections
Calls bun and node

What it does

All user-visible text in the project has to go through i18n. Before any work, the agent reads `src/common/config/i18n-config.json`, which holds the supported languages, the translation modules and the reference language (en-US at the time of writing). The agent never assumes a fixed list, because that file is the single source of truth for scripts and runtime code.

Keys use namespaced dot notation such as `t('common.send')` or `t('cron.status.active')`, and inside each module's JSON file they may be flat or nested. Names are camelCase, related keys are grouped by nesting, and reusable words like save, cancel and delete belong in `common.json`. The skill also lists common suffixes (title, placeholder, label, success and error, confirm, empty, tooltip) and then begins a step-by-step workflow, reading the config and checking existing keys, which the excerpt cuts off.

When your agent uses it

Adding new user-facing text to an existing screen
Creating a component that contains labels, titles or messages
Reviewing a pull request for hard-coded strings
Adding a new translation module

Example prompts

“Add a delete confirmation dialog to the task list and make the text translatable.”
“Review this settings component for hard-coded strings that should go through t().”
“Create a new translation module for the scheduled tasks page.”

Requirements

A project with `src/common/config/i18n-config.json` and i18next

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Read src/common/config/i18n-config.json
Check Existing Keys
Choose the Right Module
Add to ALL Locale Directories
Use in Component
Regenerate Types and Validate

What it can do on your machine

Read from SKILL.md and the folder at commit 6744099. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- bun
- node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Internationalization Workflow with i18n loads about 1.9k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 641 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~63
When it runs · the whole SKILL.md, loaded when a task matches: ~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from iOfficeAI/AionUi at commit 6744099, republished under its Apache-2.0 licence (© iOfficeAI). 641 words, ~1,939 tokens.

Download SKILL.mdSave it as .claude/skills/i18n/SKILL.md (or your agent's skills folder).

name: i18n
description: 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.

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 languages: defined by supportedLanguages array — read the file to get the current list
Modules: defined by modules array — read the file to get the current list

Key Structure

Keys use namespaced dot notation in code: t('module.key') or t('module.nested.key').

Inside each module JSON file, keys can be flat or nested:

json

// common.json — flat keys
{
  "send": "Send",
  "cancel": "Cancel",
  "copySuccess": "Copied"
}

// cron.json — nested keys
{
  "scheduledTasks": "Scheduled Tasks",
  "status": {
    "active": "Active",
    "paused": "Paused"
  }
}

In code:

typescript

t('common.send'); // flat key in common.json
t('cron.status.active'); // nested key in cron.json

Key Naming Rules

Use camelCase for key names: copySuccess, scheduledTasks
Group related keys with nesting: status.active, actions.pause
Reusable text goes in common.json: save, cancel, delete, confirm, etc.
Feature-specific text goes in the corresponding module

Common Suffixes

Suffix	Usage
`title`	Section/page titles
`placeholder`	Input placeholders
`label`	Form labels
`success` / `error`	Status messages
`confirm`	Confirmation dialogs
`empty`	Empty state messages
`tooltip`	Tooltip text

Adding New Text — Workflow

Step 1: Read `src/common/config/i18n-config.json`

Get the current language list and module list. Do not skip this step.

Step 2: Check Existing Keys

Before adding a new key, search for similar existing keys:

bash

grep -r "keyword" src/renderer/i18n/locales/en-US/

Reuse common.* keys when possible.

Step 3: Choose the Right Module

Match the module to the feature area. If no module fits, consider whether a new module is needed (see "Adding a New Module" below).

Step 4: Add to ALL Locale Directories

CRITICAL: Every new key must be added to every locale in supportedLanguages. Use this checklist for each key:

en-US/<module>.json — reference language (added in Step 3)
zh-CN/<module>.json — added
zh-TW/<module>.json — added
Any other language listed in src/common/config/i18n-config.json → supportedLanguages — added

A key missing from even one locale will cause node scripts/check-i18n.js to fail in CI.

Step 5: Use in Component

tsx

import { useTranslation } from 'react-i18next';

function MyComponent() {
  const { t } = useTranslation();
  return <button>{t('common.save')}</button>;
}

Step 6: Regenerate Types and Validate

Run these two commands in order — both must pass before committing:

bash

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

i18n:types must be run before check-i18n.js — the check validates the generated file
If check-i18n.js exits with errors (❌), fix them before proceeding
If check-i18n.js exits with warnings only (⚠️), review but may proceed
Never commit with a stale i18n-keys.d.ts

Show full SKILL.md (243 more words)Show less

Adding a New Module

Add module name to src/common/config/i18n-config.json → modules array
Create <module>.json in every locale directory (read supportedLanguages to know which)
Add import + export in each locale's index.ts
Run bun run i18n:types to regenerate type definitions
Run node scripts/check-i18n.js to validate

Hardcoded String Detection

Prohibited Patterns

Never use hardcoded Chinese/English text in JSX:

tsx

// Bad
<span>重命名</span>
<span>Delete</span>
{name || '新对话'}

// Good
<span>{t('common.rename')}</span>
<span>{t('common.delete')}</span>
{name || t('conversation.newConversation')}

Exceptions

Code comments (any language OK)
console.log() / debug output
Internal string constants not shown to users

Interpolation

Variables

json

{
  "taskCount": "{{count}} task(s)",
  "greeting": "Hello, {{name}}!"
}

tsx

t('cron.taskCount', { count: 5 });

HTML in Translations

Use Trans component for complex markup:

tsx

import { Trans } from 'react-i18next';

<Trans i18nKey='cron.countdown'>
  Task <strong>{{ taskName }}</strong> in <span>{{ countdown }}</span>
</Trans>;

zh-TW Maintenance

Most terms can be auto-converted from zh-CN, but some need manual review:

zh-CN	zh-TW	Notes
视频	影片	Different term
软件	軟體	Different term
信息	訊息	Different term
默认	預設	Different term

Quick Checklist

Before submitting code with new text:

Read src/common/config/i18n-config.json to get current languages and modules
All user-visible text uses t() function
New keys added to every locale directory in supportedLanguages
No hardcoded Chinese/English in JSX
zh-TW reviewed for term differences
bun run i18n:types ran first (regenerates i18n-keys.d.ts)
node scripts/check-i18n.js passed after types regenerated (no errors)

Common Mistakes

Mistake	Correct
Assuming a fixed number of languages	Always read `i18n-config.json` first
Adding key to only some locales	Add to every locale in `supportedLanguages`
Editing `i18n-keys.d.ts` manually	Run `bun run i18n:types` to generate
Using `t("New Chat")`	Define key: `t("conversation.newChat")`
Not updating `i18n-config.json` for new module	Update config first, then create files
Adding module JSON but not updating `index.ts`	Must add import + export in each locale's `index.ts`

Files

Just SKILL.md in .claude/skills/i18n of iOfficeAI/AionUi.

Open the folder on GitHubat commit 6744099

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in iOfficeAI/AionUi, which our catalogue first saw on October 7, 2026.

FerroxLabs/wayland.claude/skills/i18n

Compare with similar skills

Internationalization Workflow with i18n next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Internationalization Workflow with i18n compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Internationalization Workflow with i18n this skilliOfficeAI/AionUi	33k	1 repos	~1.9k	Automated safety check: Pass	Apache-2.0	1 mo ago
Chatbox i18n Translatorchatboxai/chatbox	42k	—	~508	Automated safety check: Pass	GPL-3.0	15 days ago
Enforce Rules For I18nmoeru-ai/airi	50k	—	~1.5k	Automated safety check: Pass	MIT	today
Claude Desktop Chinese Localizationjavaht/claude-desktop-zh-cn	7.5k	—	~1.6k	Automated safety check: Pass	MIT	4 days ago
Translation ReviewDevolutions/UniGetUI	26k	—	~1.3k	Automated safety check: Pass	MIT	today
Frontend I18nlangflow-ai/langflow	155k	—	~1k	Automated safety check: Pass	MIT	today

Similar skills

Chatbox i18n Translator
chatboxai/chatbox
Translates new or changed i18n keys from a Chatbox Pro diff, staged changes or a commit range, writing the locale JSON files directly with a built-in glossary.
42k GitHub stars~508 tokensUpdated 15 days ago
Frontend & DesignAuto-check passed
Enforce Rules For I18n
moeru-ai/airi
Review pending AIRI translations on Crowdin in a batch, then sync them into the repository.
50k GitHub stars~1.5k tokensUpdated today
Frontend & DesignAuto-check passed
Claude Desktop Chinese Localization
javaht/claude-desktop-zh-cn
Adds missing Simplified and Traditional Chinese translations to the Claude Desktop Chinese patch across three layers, then checks how many mappings actually hit.
7.5k GitHub stars~1.6k tokensUpdated 4 days ago
Frontend & DesignAuto-check passed
Translation Review
Devolutions/UniGetUI
Reviews UniGetUI .json language files for localization quality, detects parity issues, English-equal entries, wrong-script content, and cross-language outliers, then generates a dataset for…
26k GitHub stars~1.3k tokensUpdated today
Frontend & DesignAuto-check passed
Frontend I18n
langflow-ai/langflow
Add, change, or review user-facing text in the Langflow frontend using the i18n system (i18next / react-i18next).
155k GitHub stars~1k tokensUpdated today
Frontend & DesignAuto-check passed
Readme I18n
Y80/bmm
A skill your agent uses when the user wants to translate a repository README, make a repo multilingual, localize docs, add a language switcher, internationalize the README, or update localized…
344 GitHub starsUsed in 2 repos~1.9k tokens
Frontend & DesignAuto-check passed

Questions about Internationalization Workflow with i18n

What does Internationalization Workflow with i18n do?

Standards for keeping all user-facing text translatable: read the i18n config first, use namespaced keys, reuse shared strings and follow the key naming rules. All user-visible text in the project has to go through i18n.json`, which holds the supported languages, the translation modules and the reference language (en-US at the time of writing).

When should I use Internationalization Workflow with i18n?

Internationalization Workflow with i18n fits situations like: adding new user-facing text to an existing screen; creating a component that contains labels, titles or messages; reviewing a pull request for hard-coded strings; adding a new translation module.

How do I install Internationalization Workflow with i18n in Claude Code?

Run `npx skills add iOfficeAI/AionUi --skill i18n -a claude-code`. Or copy the skill folder (.claude/skills/i18n in iOfficeAI/AionUi) into .claude/skills/i18n in your project. Claude Code loads it when a task matches its description.

How do I install Internationalization Workflow with i18n in Codex?

Run `npx skills add iOfficeAI/AionUi --skill i18n -a codex`. Or copy the skill folder (.claude/skills/i18n in iOfficeAI/AionUi) into .agents/skills/i18n in your project. Codex loads it when a task matches its description.

Can I use Internationalization Workflow with i18n in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add iOfficeAI/AionUi --skill i18n -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/i18n, .gemini/skills/i18n, .github/skills/i18n and .opencode/skills/i18n in your project.

What does Internationalization Workflow with i18n need to run?

Going by SKILL.md and its folder, Internationalization Workflow with i18n needs the command-line tools its instructions call (bun and node). Our summary lists: A project with `src/common/config/i18n-config.json` and i18next.

Does Internationalization Workflow with i18n access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Internationalization Workflow with i18n safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Internationalization Workflow with i18n use?

Internationalization Workflow with i18n is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Internationalization Workflow with i18n use?

About 1.9k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Internationalization Workflow with i18n?

Skills that share tags, products or a category with Internationalization Workflow with i18n: Chatbox i18n Translator (chatboxai/chatbox, 42k stars), Enforce Rules For I18n (moeru-ai/airi, 50k stars), Claude Desktop Chinese Localization (javaht/claude-desktop-zh-cn, 7.5k stars) and Translation Review (Devolutions/UniGetUI, 26k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Internationalization Workflow with i18n?

iOfficeAI (a GitHub organization) maintains it in iOfficeAI/AionUi, which has 33,409 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 9, 2026.

Source: iOfficeAI/AionUi on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Internationalization Workflow with i18n

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

i18n Skill

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

Hardcoded String Detection

Prohibited Patterns

Exceptions

Interpolation

Variables

HTML in Translations

zh-TW Maintenance

Quick Checklist

Common Mistakes

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from iOfficeAI/AionUi

Related

Questions about Internationalization Workflow with i18n

Step 1: Read `src/common/config/i18n-config.json`