How do I install the I18N skill?

Run npx skillmds@latest add project-n-e-k-o/i18n in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with I18N?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

project-n-e-k-o (@project-n-e-k-o) published this skill. Their other Agent Skills are listed on their SkillMD profile.

I18N by project-n-e-k-o — Agent Skill

Name: I18N
Author: project-n-e-k-o

I18N

i18n (internationalization) toolkit for projects using i18next. Provides three main functions: (1) i18n-check - Detect hardcoded Chinese text in HTML/JS files, (2) i18n-fix - Replace hardcoded text with i18n markers, (3) i18n-sync - Align translation keys across multiple languages (zh-CN, zh-TW, en, ja, ko, ru, es, pt). Use when working on internationalization tasks, detecting untranslated strings, or syncing locale files.

project-n-e-k-o b66032e 3 files · 5.4 KB Updated Sep 17, 2026

File contents

i18n Toolkit

Complete i18n (internationalization) toolkit for projects using i18next.

Architecture

i18n library: i18next
Locale files: static/locales/ (zh-CN, zh-TW, en, ja, ko, ru, es, pt)
HTML attributes: data-i18n, data-i18n-placeholder, data-i18n-title, data-i18n-alt
JS function: window.t() or i18next.t()
Progress file: .claude/i18n-progress.json

Three Main Commands

1. i18n-check - Detect Issues

Check frontend files for hardcoded Chinese text.

/i18n-check <module> [options]

Modules: main, live2d, voice, steam, settings, chat, custom

Options: --status, --reset, --files=<path>, --html, --js, --strict

See references/check-modules.md for module file mappings.

2. i18n-fix - Fix Issues

Replace hardcoded Chinese with i18n markers.

/i18n-fix <module> [--add-keys]

Fix patterns:

HTML: Add data-i18n="key" attributes
JS: Use window.t('key') with fallback

See references/fix-patterns.md for examples.

3. i18n-sync - Sync Languages

Align translation keys across all languages.

uv run python scripts/i18n_sync.py          # Check status
uv run python scripts/i18n_sync.py --apply  # Apply changes

Quick Workflow

Check: /i18n-check steam - Find hardcoded strings
Fix: /i18n-fix steam - Replace with i18n markers
Verify: /i18n-check steam - Confirm fixes
Sync: /i18n-sync - Sync to other languages

Detection Rules

Check for:

HTML: Chinese text in elements or attributes
JS: Chinese strings not wrapped in window.t()

Skip:

Already has data-i18n* or window.t() wrapper
console.log/error/warn debug messages
Third-party libs (static/libs/)
Comments
Internal logic strings (e.g., includes('已离开'))
Data keys (e.g., data['档案名'])

---name: i18ndescription: i18n (internationalization) toolkit for projects using i18next. Provides three main functions: (1) i18n-check - Detect hardcoded Chinese text in HTML/JS files, (2) i18n-fix - Replace hardcoded text with i18n markers, (3) i18n-sync - Align translation keys across multiple languages (zh-CN, zh-TW, en, ja, ko, ru, es, pt). Use when working on internationalization tasks, detecting untranslated strings, or syncing locale files.---# i18n ToolkitComplete i18n (internationalization) toolkit for projects using i18next.## Architecture- **i18n library**: i18next- **Locale files**: `static/locales/` (zh-CN, zh-TW, en, ja, ko, ru, es, pt)- **HTML attributes**: `data-i18n`, `data-i18n-placeholder`, `data-i18n-title`, `data-i18n-alt`- **JS function**: `window.t()` or `i18next.t()`- **Progress file**: `.claude/i18n-progress.json`## Three Main Commands### 1. i18n-check - Detect IssuesCheck frontend files for hardcoded Chinese text.```/i18n-check <module> [options]```**Modules**: main, live2d, voice, steam, settings, chat, custom**Options**: `--status`, `--reset`, `--files=<path>`, `--html`, `--js`, `--strict`See [references/check-modules.md](references/check-modules.md) for module file mappings.### 2. i18n-fix - Fix IssuesReplace hardcoded Chinese with i18n markers.```/i18n-fix <module> [--add-keys]```**Fix patterns**:- HTML: Add `data-i18n="key"` attributes- JS: Use `window.t('key')` with fallbackSee [references/fix-patterns.md](references/fix-patterns.md) for examples.### 3. i18n-sync - Sync LanguagesAlign translation keys across all languages.```bashuv run python scripts/i18n_sync.py # Check statusuv run python scripts/i18n_sync.py --apply # Apply changes```## Quick Workflow1. **Check**: `/i18n-check steam` - Find hardcoded strings2. **Fix**: `/i18n-fix steam` - Replace with i18n markers3. **Verify**: `/i18n-check steam` - Confirm fixes4. **Sync**: `/i18n-sync` - Sync to other languages## Detection Rules### Check for:- HTML: Chinese text in elements or attributes- JS: Chinese strings not wrapped in `window.t()`### Skip:- Already has `data-i18n*` or `window.t()` wrapper- `console.log/error/warn` debug messages- Third-party libs (`static/libs/`)- Comments- Internal logic strings (e.g., `includes('已离开')`)- Data keys (e.g., `data['档案名']`)

Frequently asked questions