translatelisted

Translate any project or set of files into one or more target languages using the three-tier translator panel (Lead → Senior/Junior with adversarial QA). Works on codebases (i18n message catalogs, WordPress .po/.pot/.json, MDX/HTML content trees) and standalone documents (Markdown, JSON, docx, txt, subtitles, CSV). Detects the source language and file formats, computes the translation scope (whole project, changed-since-last-run, or an explicit file/glob set), classifies each batch as low-risk (Junior) or domain-prose (Senior), and applies the domain SPECIALIZATION setting (default `general`; e.g. technical, marketing, legal). Runs one final verify/build at the end and writes a report. Use when the user says "translate this", "translate into <language>", "localize the project", "run the translation pass", "translate the WordPress strings", "translate these files", or "i18n sweep".
roshaw/claude-translation-agency · ★ 2 · Data & Documents · score 75

Install: claude install-skill roshaw/claude-translation-agency

# translate The single entry point for translating **anything** — a whole codebase's i18n, a WordPress theme/plugin's gettext catalog, a folder of Markdown docs, a batch of JSON files, a subtitle file — into **any** set of target languages. It drives the three-tier translator panel and applies a domain **specialization** so terminology is right for the material. ## The panel (why three tiers) - **Lead** (`translate-lead`, Opus) — orchestrates the run, dispatches each batch to a worker, and **adversarially reviews** every result against a fixed C1–C7 checklist before signing off. Runs the final blind-spot sweeps. Loads the specialization module so its terminology check is domain-aware. - **Senior** (`translate-senior`, Sonnet) — translates domain-prose and any substantive surface. Spawned by the Lead, not directly by this skill. - **Junior** (`translate-junior`, Haiku) — translates only low-risk UI chrome. Spawned by the Lead. This skill computes the scope + per-batch tier classification, then spawns the **Lead once**; the Lead handles all worker spawns and reviews. The single final build/verify runs here (Step 6). ## Invocation ``` /translate # translate the changed-since-last-run set into the configured targets /translate --path <dir> # point at a project/folder on disk, e.g. --path C:\Projects\MyApp /translate <path> # shorthand for --path <path> (a folder) or --files <path> (a file/glob) /translate --to <lan