ccc-buildlisted

# /ccc-build — Scaffold a project Click-first build flow. Four templates, one spec interview, one background agent. User clicks a tile, answers 3 questions, walks away — the scaffold lands in their worktree while they wait. ## Response shape (EVERY time) Output exactly these three sections in order: ### 1. Brand header (one line, markdown) ``` **CC Commander** · /ccc-build · Scaffold a project or feature ``` ### 2. Context strip (one paragraph) Detect target location with **three quick reads** (parallel Bash, silent on failure): - `git rev-parse --abbrev-ref HEAD` → branch - `ls -1 | head -20` → repo inventory (empty repo? existing project?) - `test -f package.json && cat package.json | head -5` → detect existing stack Render one line: > 🧭 Target: `<cwd basename>` · branch: `<branch>` · <empty repo | Node project | Python project | other> If an existing project is detected, add a gentle note: "I'll scaffold into a sub-directory so I don't clobber your current code." ### 3. The picker — `AskUserQuestion` with 4 templates Read `${CLAUDE_PLUGIN_ROOT}/menus/ccc-build.json` for canonical option data. Surface exactly 4 of the 5 non-back choices (drop "mobile" if the user's stack is backend-only; otherwise keep web-app / api / cli / mobile). ``` question: "What are we building?" header: "CC Commander Build" multiSelect: false options: - label: "🌐 Web app" description: "Next.js + Tailwind + shadcn/ui — SSR, auth, Stripe-ready." preview: "Best for: product site