i18n-sync

Use this skill when you need to keep i18n keys in sync across frontend, backend, iOS, and Android.

Contract

• Function pattern: i18n("key", { count: 0, name: userName })
• Function name is fixed to i18n
• Second argument must be an object/map literal
• Translation storage is always flat JSON: { "key": "value with {param}" }
• API auth token is not required; fetch by projectKey

Commands

• i18n-sync extract
• i18n-sync validate
• i18n-sync sync
• Optional overrides: --project-key <key>, --url <api-url>

Required setup

Before running commands, create this file in the execution directory:

• ./i18n.config.json

Required fields:

• api.url
• api.requestBody.projectKey

If ./i18n.config.json does not exist, the CLI exits and prompts user to create it.

What it does

1. Extract keys and params from source code.
2. Pull all project translation JSON from API once.
3. Filter translations by extracted keys.
4. Validate placeholders (translation side vs code side).
5. Emit locale JSON into <dir>/i18n/.

Default backend endpoint in this repository: POST /api/i18n/translations.

Artifacts

• .i18n-artifacts/report.json
• Optional (disabled by default): .i18n-artifacts/keys.json