groot runs each framework's official generator — create-next-app, sv, create-expo-app, create-hono, Convex — and stitches the output into one coherent bun workspace. No vendored templates. Nothing to rot.
Bun ≥ 1.2. Or grab the standalone binary — no Bun needed to run it.
Pick per slot. Every combination arrives wired: workspace links, deconflicted ports, one lockfile.
A strict pipeline — every stage succeeds completely or fails precisely. Architecture →
Official generators, pinned majors, silence flags. Your day-1 output is today's framework — not a template frozen last spring.
Package names, workspace links, dev ports, turbo outputs, env plumbing, one root lockfile — and a groot.json manifest as memory.
Structure checks, real install, git init. Later: groot doctor re-checks health any time, with suggested fixes.
groot add honoGrow another scaffold into an existing workspace — occupancy-checked, cross-wired by the same idempotent stitch, rolled back surgically on failure.
groot doctor --jsonHealth checks with suggested fixes: ports, lockfiles, manifests, per-framework invariants. Exit 0 or 5 — drops straight into CI.
groot init --preset ../flagshipReplicate any workspace's shape from its groot.json. Generator pins always come from the CLI you run — presets never freeze upstream.
Scriptability is a first-class feature, tested at the process level. Recipes →