grouter: Skill for Claude Code

grouter — Install & First-Run Flow

Get a user from zero to a running grouter serve with a working proxy at http://localhost:3099. There are four install paths — pick one with the user, don't run all of them.

Ground rules

1. Never sudo. grouter installs to the user's ~/.bun/bin (or runs in a container). If a command seems to need root, stop and ask.
2. Never overwrite the user's shell config silently. PATH fixes get printed as a one-liner for the user to run, not injected.
3. Don't wipe ~/.grouter/. That's where accounts and the SQLite DB live. Uninstall removes the binary only unless the user explicitly asks to drop data.
4. Verify at each step. After install, confirm grouter --version works before moving to first-run.
5. Confirm before actions that touch global state (global bun install -g, bun link, docker compose up, writing to ~/.claude/settings.json).

Step 0 — Detect the environment

Run in parallel:

bun --version 2>/dev/null || echo "NO_BUN"
docker --version 2>/dev/null || echo "NO_DOCKER"
command -v grouter && grouter --version 2>/dev/null || echo "NO_GROUTER"
echo "$PATH" | tr ':' '\n' | grep -E "\.bun/bin$" || echo "BUN_BIN_NOT_IN_PATH"
uname -s

Decision:

State	Recommend
bun present, user just wants to try	Path A — bunx
bun present, user wants permanent install	Path B — global install
Inside a clone of the repo, contributor	Path C — from source
docker present, no bun, or user prefers containers	Path D — docker
Neither bun nor docker	Stop — install Bun (curl -fsSL https://bun.sh/install | bash) or Docker first. Tell the user which.

If grouter is already on PATH, ask whether the user wants to upgrade (rerun their original install path) or reinstall fresh (uninstall → install).

Path A — bunx (one-shot, no install)

Best for: "just let me try it".

bunx grouter-auth setup

That's it. No global install, no PATH fiddling. Skip to Step 2 (first-run) — bunx runs the setup wizard directly.