skills.rest
Hsiung-Shao
Hsiung-ShaoCOMMUNITY
Explore all skills by this author →
𝕏@HsiungshaoGitHub

i18n-consistency

Propagate translation key changes from zh-TW to other locales and verify consistency.

Updated Aug 27, 2026
Search Tags:#consistency#verification#localization#translation#i18n#locales
One-click install
npx skills add https://github.com/Hsiung-Shao/Multi-Stream --skill i18n-consistency
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: i18n-consistency
Source: https://github.com/Hsiung-Shao/Multi-Stream/tree/main/.agent/skills/i18n-consistency
Command: npx skills add https://github.com/Hsiung-Shao/Multi-Stream --skill i18n-consistency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures translation keys stay consistent across all supported locales, preventing drift between source zh-TW and other languages.

Core Features & Use Cases

  • Key synchronization: Detect missing or mismatched keys across zh-CN, en, ja, and ko and align
  • Namespace-aware: Works with locale files organized by namespaces under src/i18n/locales/
  • Verification: Provides a configurable workflow to propagate changes and verify integrity with a script

Quick Start

Analyze zh-TW changes, propagate to other locales, and run the verification script to confirm all keys are in sync.

Frequently Asked Questions about i18n-consistency

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

FAQPage Schema
How do I keep translation keys consistent across multiple locale files?▼

To keep translation keys consistent, you propagate changes from a source locale like zh-TW to target locales such as zh-CN, en, ja, and ko, enforcing key synchronization and detecting missing or mismatched keys.

How do I detect missing i18n keys in different languages?▼

You detect missing i18n keys by running a verification workflow that compares structured locale files against the source zh-TW, identifying any keys that are absent or mismatched in target languages.

Does this locale verification workflow work with namespace-organized translation files?▼

Yes, this locale verification workflow works with namespace-organized translation files stored under the src/i18n/locales/ directory, applying key synchronization across these structured multi-language projects.

What is the best way to propagate i18n updates from a source language to others?▼

The best way to propagate i18n updates is to apply changes made in the source zh-TW locale file and automatically align the translation keys across zh-CN, en, ja, and ko, followed by a verification script.

Why do my translation keys drift between different locale files?▼

Translation keys drift when updates are applied to the source locale without propagating the structural changes to other languages, which you prevent by enforcing key synchronization from zh-TW to all target locales.

Related Skills

Explore More Content & Communication Skills→
StarrySerendipityStarrySerendipity

i18n

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

Community
Intermediate
eaglhuangeaglhuang
3

ui-i18n-localize

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

Community
Intermediate
emavglemavgl
419

translate

Translate untranslated strings in locale JSON files using source code context.

Community
Intermediate
HankanmanHankanman
1

nextjs-intl-translation-structure-consistency

Validate translation-key structures across Next.js locale JSON files.

Community
Intermediate