init-projectlisted

# init-project — configure a freshly spawned starter project The starter template ships with placeholder sections that MUST be configured before the kernel rules are trustworthy. This skill is the guided path: detect what's detectable, ask only what isn't, write it down, and verify the setup. Run it ONCE per spawned project. If `grep -c "FILL IN" CLAUDE.md` returns 0, the project is already configured — say so and exit. ## Step 0: Confirm this is a spawned project Check `git remote get-url origin` before changing files. If it points to `ryanportfolio/AI-Firmware` (or the old name `ryanportfolio/claude-starter`), this is the canonical template: do not initialize, delete template assets, prune skills, or rewrite its generic defaults. Explain that the markers are intentional and stop. If the repo still has the canonical `# Agent firmware` README plus both `bootstrap/` and `.claude-plugin/`, ask whether this is a template checkout or maintenance fork versus a spawned project, regardless of its origin name. Do not delete those assets until the user confirms it is spawned. Their answer is authoritative; repository names alone are ambiguous. ## Step 1: Detect the stack (no questions yet) Look before asking. Gather from the repo itself: - `ls` the root — what scaffold exists? (`package.json`, `pyproject.toml`, `Cargo.toml`, `go.mod`, `*.csproj`, nothing yet?) - If `package.json` exists: read `scripts` (build/dev/test/check commands), `dependencies` (framework, router, query l