translate-initlisted

Guided, step-by-step builder for a project's translation.config.json — the setup step before /translate. Walks the operator through every option ONE AT A TIME with a plain-language explanation of what it does and what to fill, pre-filling smart defaults it detects from the project (source language, formats, existing target languages). Captures the project's PURPOSE/CONTEXT (what the product is, so the translator picks the right sense of each word), the target languages, domain specialization, output layout, and the research/uncertainty preferences. Writes the config at the project's root and registers the folder as a tracked project. Use when the user says "set up translation for this project", "create the translation config", "configure translations", "initialize translation", "build the config step by step", or before a first /translate run on a project with no config.
roshaw/claude-translation-agency · ★ 2 · AI & Automation · score 73

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

# translate-init A **guided wizard** that builds `translation.config.json` at the **root of the project being translated** (the target project — the folder with the source files) and registers that folder as a tracked project. It asks about each option one step at a time, explaining what the option does and what to put, and pre-fills what it can detect. Run it once per project, then run `/translate`. > **Placement is the whole point.** The file goes in the **target project**, not in the Translation > Agency toolkit folder. Pointing at `C:\Projects\MyApp` writes `C:\Projects\MyApp\translation.config.json`. ## Invocation ``` /translate-init # set up the current folder as the target project /translate-init --path <dir> # set up a specific project, e.g. --path C:\Projects\MyApp /translate-init <path> # shorthand for --path ``` ## Step 0 — Resolve the target project root `--path` / bare `<path>` → that folder; else the current directory (accept an absolute computer path as given). This root is where the config is written. If a `translation.config.json` **already exists**, read it and offer to update it (its current values become the defaults) — never silently clobber. ## Step 1 — Detect, so defaults are pre-filled (don't ask what you can infer) Using `Glob`/`Grep`/`Read` (never shell loops), infer: **source language** (`messages.en.ts`, `en/`, `.en.md`, `-en.po`, or a content sample; default `en`); **existing target languages** already