translation-i18n

Layer 2-5 owner for i18n format files in translation-toolkit. Reads an intake-spec produced by translation-intake (Layer 1), parses one of five i18n format families, runs the shared DRAFT / REFLECT / IMPROVE core loop with strict placeholder + project-glossary preservation, and writes back into the original format.

Inputs

• source — file path (one of .po / .json / .xliff / strings.xml / .strings) or an inline strings map keyed by ID.
• intake-spec — from translation-intake. If the user invokes this skill directly without one, run intake first (--intake flag) before continuing.
• glossary_path (optional) — repo-local project glossary (L1 tier of the 4-tier resolver). Defaults to <caller_repo>/docs/i18n/glossary-{target_locale}.md; missing → fall through to L2 bundled glossary in glossary/.

Service-interface contract (the four shared fields plus web_search) is defined in the design spec §Service Interface; no per-skill duplication here.

When to use

• Routed in by using-translation-toolkit when the user supplies a PO / JSON / XLIFF / Android strings.xml / iOS .strings file.
• Invoked directly by name when the user already knows i18n is the right specialist.
• Not for prose / Markdown docs (use translation-doc), ad copy / catchphrases (use translation-creative), or reviewing an existing translation pair (use translation-audit).

Web search policy