How do I install the I18N Sync skill?

Run npx skillmds@latest add ksmaster03/i18n-sync 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.

Is I18N Sync safe to use?

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 Sync?

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.

Is I18N Sync free to use?

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

Who published I18N Sync?

ksmaster03 (@ksmaster03) published this skill. Their other Agent Skills are listed on their SkillMD profile.

I18N Sync by ksmaster03 — Agent Skill

Name: I18N Sync
Author: ksmaster03

I18N Sync

Add or sync i18n translation keys across all locale files (EN + TH) in any monorepo with parallel locale JSON (next-intl, i18next, React Native). Detects missing/orphan keys, keeps EN/TH in lockstep, and fills Thai translations. Trigger when the user types /i18n-sync, asks to "add a translation / เพิ่มคำแปล / sync i18n / ใส่ภาษา / แปล key", or edits locale files and risks leaving a locale out of sync.

ksmaster03 Updated Sep 21, 2026

File contents

/i18n-sync — keep locale files in lockstep

Adding a UI string means touching every locale file or the app throws a missing-key warning. This skill does it once, correctly, in EN + TH.

Locate the locale files first

Don't assume — discover per app, because web and mobile differ:

Web (Next.js / next-intl): typically messages/en.json + messages/th.json (nested namespaces).
Mobile (React Native): grep for i18n, translations, locales/ under the mobile app — structure may be flat or per-namespace.
Shared strings: check any packages/shared for cross-app message constants.

If the layout differs, glob for **/messages/*.json, **/locales/*.json, or en.json/th.json pairs and infer the convention from what exists.

Procedure

Read every locale file in the target app so you see the real key tree and namespace style.
Place the new key in the namespace that matches sibling keys (don't invent a new top-level namespace unless asked).
Write all locales together — EN (technical/source) and TH. For TH use natural business Thai, not literal machine translation.
Keep key order identical across locale files so diffs stay reviewable.
Report the keys added and any pre-existing drift you noticed.

Audit mode (when asked "are translations in sync?")

Diff the key sets of each locale pair. List: keys in EN missing from TH (and vice-versa), and orphan keys not referenced in code (grep the key string).
Output a table: key | en | th | status (missing-th / orphan / ok).

Gotchas

⚠️ Thai text in JSON must stay UTF-8 — never let an editor save as cp1252 (the classic Windows trap).
next-intl keys are referenced as t('namespace.key') — when adding, grep the namespace to confirm it exists before nesting.
Don't reorder or reformat unrelated keys; minimise the diff.

---name: i18n-syncdescription: Add or sync i18n translation keys across all locale files (EN + TH) in any monorepo with parallel locale JSON (next-intl, i18next, React Native). Detects missing/orphan keys, keeps EN/TH in lockstep, and fills Thai translations. Trigger when the user types /i18n-sync, asks to "add a translation / เพิ่มคำแปล / sync i18n / ใส่ภาษา / แปล key", or edits locale files and risks leaving a locale out of sync.---# /i18n-sync — keep locale files in lockstepAdding a UI string means touching **every** locale file or the app throws a missing-key warning. This skill does it once, correctly, in EN + TH.## Locate the locale files firstDon't assume — discover per app, because web and mobile differ:1. **Web (Next.js / next-intl):** typically `messages/en.json` + `messages/th.json` (nested namespaces).2. **Mobile (React Native):** grep for `i18n`, `translations`, `locales/` under the mobile app — structure may be flat or per-namespace.3. **Shared strings:** check any `packages/shared` for cross-app message constants.If the layout differs, glob for `**/messages/*.json`, `**/locales/*.json`, or `en.json`/`th.json` pairs and infer the convention from what exists.## Procedure1. **Read every locale file in the target app** so you see the real key tree and namespace style.2. **Place the new key** in the namespace that matches sibling keys (don't invent a new top-level namespace unless asked).3. **Write all locales together** — EN (technical/source) and TH. For TH use natural business Thai, not literal machine translation.4. **Keep key order identical** across locale files so diffs stay reviewable.5. **Report** the keys added and any pre-existing drift you noticed.## Audit mode (when asked "are translations in sync?")- Diff the key sets of each locale pair. List: keys in EN missing from TH (and vice-versa), and orphan keys not referenced in code (grep the key string).- Output a table: `key | en | th | status (missing-th / orphan / ok)`.## Gotchas- ⚠️ Thai text in JSON must stay UTF-8 — never let an editor save as cp1252 (the classic Windows trap).- next-intl keys are referenced as `t('namespace.key')` — when adding, grep the namespace to confirm it exists before nesting.- Don't reorder or reformat unrelated keys; minimise the diff.

Frequently asked questions