translate-init

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 present; formats present (JS/TS or JSON catalogs, WordPress .pot/.po, i18next/.arb, MD/MDX/HTML trees, subtitles, CSV); a likely include set (where translatable files actually live); a verify command (npx tsc --noEmit if there's a tsconfig); and any WordPress text domain. Print a short "here's what I found" summary before asking anything.

Step 2 — Walk the operator through each option (the guided part)

Ask about the settings one at a time, each with a one-line explanation of what it controls and what to enter, and the detected value pre-filled as the default. Use AskUserQuestion (batching a few related ones per screen is fine), but always include the explanation so the operator understands the choice. If the session is unattended, skip the prompts, use detected defaults + general + inplace + first-run research + report queries, and state the assumptions.