skills.rest
StarrySerendipity
StarrySerendipityCOMMUNITY
Explore all skills by this author →
GitHub

i18n

Detect hardcoded Chinese text in HTML/JS and replace it with i18n markers.

Updated Mar 31, 2026
Search Tags:#frontend#localization#code-quality#i18n#translations#i18next#locale-files
One-click install
npx skills add https://github.com/StarrySerendipity/N.E.K.O --skill i18n-starryserendipity
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: i18n
Source: https://github.com/StarrySerendipity/N.E.K.O/tree/main/.agent/skills/i18n
Command: npx skills add https://github.com/StarrySerendipity/N.E.K.O --skill i18n-starryserendipity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

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, en, ja, ko, zh-TW). Use when working on internationalization tasks, detecting untranslated strings, or syncing locale files.

Core Features & Use Cases

  • i18n-check: Detects hardcoded Chinese strings in frontend HTML/JS and reports locations for replacement.
  • i18n-fix: Replaces hardcoded text with i18n markers and fallback logic in code.
  • i18n-sync: Synchronizes keys across locale files (zh-CN, en, ja, ko, zh-TW) to ensure consistency.
  • Use Case: Teams migrating a project to i18n where multiple languages must be supported and kept in sync.

Quick Start

Run i18n-check on your frontend to detect hardcoded Chinese strings, then run i18n-fix to replace them with i18n markers, and finally run i18n-sync to align all locale files.

Frequently Asked Questions about i18n

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect hardcoded Chinese text in frontend HTML and JavaScript files?▼

To detect hardcoded Chinese text in frontend HTML and JavaScript files, run an i18n-check command that scans your codebase for untranslated strings and reports their exact locations for replacement.

Do I need i18next and static locale files to set up internationalization for my project?▼

Yes, you need i18next and locale files stored under a static/locales directory to set up internationalization, enabling the system to use data-i18n attributes and window.i18next.t calls.

What is the best way to sync translation keys across multiple languages like zh-CN, en, ja, ko, and zh-TW?▼

The best way to sync translation keys across zh-CN, en, ja, ko, and zh-TW is to run an i18n-sync command that aligns all locale files to ensure structural consistency and prevent missing translations.

How does replacing hardcoded text with i18n markers work in i18next?▼

Replacing hardcoded text with i18n markers works by substituting Chinese strings with data-i18n attributes or window.i18next.t calls, adding fallback logic, and logging updates to a progress file.

Can I use this i18n workflow to replace hardcoded text in any frontend framework?▼

No, this i18n workflow is specifically designed for frontend projects using i18next, requiring static/locales directory structures, data-i18n attributes, and window.i18next.t calls to function correctly.

Related Skills

Explore More Software Engineering Skills→
tegniketegnike
1.1k

sync-translations

Sync missing translation keys across locale files from a Japanese master.

Community
Basic
eaglhuangeaglhuang
3

ui-i18n-localize

Expand zh-TW UI strings to zh-CN, en, and ja while preserving placeholders.

Community
Intermediate
abhishekdutta18abhishekdutta18

plankton-code-quality

Run formatters and linters to enforce code quality during file edits.

Community
Intermediate
danilomartinellidanilomartinelli
1

i18n-localization

Detect hardcoded strings and manage translation files for software applications.

Community
Intermediate