i18n-sync

Synchronize zh-TW and en translation files with key comparison and validation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Youngger9765/young-personal-site --skill i18n-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-sync
Source: https://github.com/Youngger9765/young-personal-site/tree/main/.claude/skills/i18n-sync
Command: npx skills add https://github.com/Youngger9765/young-personal-site --skill i18n-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures perfect synchronization between Chinese (zh-TW) and English (en) translation files, preventing missing translations and structural mismatches, saving you hours of manual review.

Core Features & Use Cases

  • Automated Key Synchronization: Compare translation files and align keys across locales.
  • Missing Key Detection: Identify missing keys and propose fixes.
  • Consistency Verification: Validate structural and type consistency between locales.

Quick Start

Example prompt: "Please compare messages/zh-TW.json with messages/en.json and generate a bilingual synchronization report with fixes."

Frequently Asked Questions about i18n-sync

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

FAQPage Schema
How do I sync translation files between English and Chinese?

Translation file synchronization compares your en.json and zh-TW.json files to align keys, detect missing translations, and fix structural mismatches. Load both files, compare their key structures, validate types, check completeness, and generate a report with optional auto-fixes that preserve structure and back up originals.

What causes missing keys in bilingual JSON translation files?

Missing keys occur when new strings are added to one locale's JSON file but not propagated to the other. This Skill identifies which keys exist in English but not Chinese (or vice versa) by parsing and comparing file structures, helping you catch incomplete translations before deployment.

Can I automatically fix translation file inconsistencies?

Yes, this Skill includes auto-fix capabilities that detect and resolve inconsistent keys and structural mismatches between zh-TW and en JSON files. It applies fixes while preserving original structure and creates backups, so you can review changes safely.

How do I validate that my English and Chinese translation files match?

Validation compares JSON key structures, data types, and translation completeness across locales. This Skill performs structural and type validation, then generates a comprehensive synchronization report showing misalignments, missing entries, and consistency issues between your files.

When should I sync translation files during development?

Sync during content addition, updates, refactoring, and before/after major changes to catch missing or inconsistent translations early. This Skill auto-activates when prompts reference translation, language, or i18n concepts, and supports manual workflows for pre-deployment validation.

Do I need to manually edit JSON files to keep translations in sync?

No, manual editing creates sync errors and inconsistencies. This Skill automates the comparison and alignment process, detecting structural and key mismatches across zh-TW and en JSON files without requiring manual file edits.