Localize Strings Workflow Skill

Name: localize-strings
Rating: 87
Author: wandyezj

Use this skill when the user asks to localize new or changed UI strings in this repository.

Purpose

Apply the documented localization process in docs/localize.md and related localize/ files.

•Only localize UI strings.
•Ensure UI strings are wrapped in loc("...") before running localization tooling.
•If a language translation is missing, English is the fallback.
•Keep changes minimal and aligned with the existing project style.

•
Run string extraction:
- •npm run extract-loc
•
Perform translation directly:
- •Use localize/translate-prompt.txt as the translation prompt.
- •Generate translated TSV output.
- •Apply results to localize/strings.tsv.
•
Embed localized language resources:
- •npm run embed-loc
•
Validate output quality:
- •Spot-check changed strings in src/core/localize/strings.json and generated artifacts.
- •Confirm no obvious formatting or placeholder regressions.
•Report exactly what changed and any errors or issues encountered.

•Execute translation directly as part of the workflow; only ask the user for input if translation fails or output is ambiguous.
•
Automatically run localization commands using the platform shell:
- •Windows: run in cmd (cmd /c "npm run extract-loc" and cmd /c "npm run embed-loc").
- •macOS: run in zsh (zsh -lc "npm run extract-loc" and zsh -lc "npm run embed-loc").
•Preserve TSV formatting exactly (tabs, column order, escaping).
•Do not introduce new dependencies.
•Prefer targeted edits; avoid unrelated refactors.

•Updated localization source files (typically localize/strings.tsv, plus embedded outputs).
•
Short summary including:
- •Commands run.
- •Files changed.
- •Any manual follow-up required.
- •Any strings that remain intentionally untranslated (for example, approved brand/product names).