Set up zedkit AI in
Give your coding agent one prompt to set up zedkit AI in your project.
Who this is for
You use a coding agent (Cursor, Muse, Claude Code, Codex, or similar) on a git repo (empty or already with team rules) and want one paste to hand the agent — no back-and-forth on how to start.
Agent prompt (copy)
Paste this as the only message in a new chat at the repo root (Cursor, Muse, Claude Code, or your tool — agents should fetch https://zedkit.app/ai/setup.md):
Set up zedkit AI on this repo following https://zedkit.app/ai/setup.md
Full walkthrough: /docs/ai/setup
Agents should read the raw steps at https://zedkit.app/ai/setup.md (plain markdown, no site chrome).
This guide targets @zedtech/zedkit-ai 1.2.0 (the current published version). Every command below pins it with @1.2.0; drop the suffix to float (not reproducible).
What the agent will do
- Add
@zedtech/zedkit-ai@1.2.0if missing or not exactly at 1.2.0 (pnpm add -D -w --save-exactat a pnpm workspace root whenpnpm-workspace.yamlexists). - Run
npx @zedtech/zedkit-ai@1.2.0 setup --provider cursor(setuppreset by default, adopt mode — keeps your files on collision; override with--preset starter|setup|core|fullif needed). Use--provider muse,claude,codex, comma-separated names, orallto match your tool. - Run
/setup-ai— phases A–E (audit, batched discovery interview — answer or delegate, do not skip — buildproduct.md, domain rules, personas,design.mdwhen relevant, repo skills, score and learn), then verify and report. - Run
npx @zedtech/zedkit-ai@1.2.0 validateuntil stdout isok.
Time: about 15–45 minutes for a typical app repo once the agent starts (see the setup-ai skill intro).
Single-repo vs workspace
| Situation | Where to paste the prompt |
|---|---|
| One git repository | That repo's root |
| Workspace with several checkouts | The workspace root first; /setup-ai runs workspace mode and proposes per-repo setup inside each child |
Manual path (same result)
pnpm add -D --save-exact @zedtech/zedkit-ai@1.2.0 # workspace root: pnpm add -D -w --save-exact @zedtech/zedkit-ai@1.2.0
npx @zedtech/zedkit-ai@1.2.0 setup --provider cursorThen /setup-ai in your agent, then:
npx @zedtech/zedkit-ai@1.2.0 validateAlready on 1.1.x?
Re-run npx @zedtech/zedkit-ai@1.2.0 setup (adopt keeps your files; kit copies
land as *.kit.md / zk-<name>), then /setup-ai. Coming from 0.12? Follow
Upgrading from 0.12.
Opt-in npx @zedtech/zedkit-ai@1.2.0 validate --setup checks plan coverage, gate-log shape, and that the
setup went deep: /setup-ai reads the code first with read-only subagents
(npx @zedtech/zedkit-ai@1.2.0 scan sizes them), writes domain rules and nested AGENTS.md
files from what they found, fills .agents/tokenomics.md (cheap models on
check/build at trivial/standard, the strong model on sensitive/critical),
and runs npx @zedtech/zedkit-ai@1.2.0 sync.
Troubleshooting
| Symptom | What to check |
|---|---|
validate not ok | Run from repo root; fix each path: message line or re-run setup after resolving collisions. |
Agent skips /setup-ai | Paste the prompt again; mechanical install alone is not done. |
| Unknown provider | Use cursor, claude, codex, muse, all, or comma-separated names only. |
Next steps
- Set up your coding agents — full CLI tutorial (presets, undo, providers)
- Set up AI agent instructions — catalog reference