bootstrap-projectlisted

Crystallize a project-design conversation into a complete project scaffold. Reads the current session for project name, principles, milestones, stack, and audience; writes the docs/ quintet (PROJECT, ARCHITECTURE, ROADMAP, PROGRESS, DEPLOY), CLAUDE.md, Makefile, CI workflow, pre-commit config, VERSION, LICENSE, CHANGELOG, and supporting files. Supports stack profiles for Python, Node, Go, Rust, polyglot, and Nix flakes; deploy models for docker-compose, single binaries, artifacts (OS images / appliances), and libraries. Use this when the user says "bootstrap this project", "scaffold the repo", "now write all of this down", or invokes /bootstrap-project. The skill is a finalizer — it assumes the design conversation has happened in this session and extracts spec from context. It will ask only the minimum follow-ups (license, optional add-ons, profile-specific questions, anything missing). Do NOT use this for: existing projects (the skill refuses to clobber files); greenfield brainstorming (have the design conve
joseluisamado/bootstrap-project-skill · ★ 0 · AI & Automation · score 58

Install: claude install-skill joseluisamado/bootstrap-project-skill

# bootstrap-project This skill produces a project scaffold whose shape comes from libreta's engineering conventions, refined and extended. The full playbook lives in [`INSTRUCTIONS.md`](./INSTRUCTIONS.md). Read it when the skill is invoked. The short version: 1. Extract a project spec from the current conversation. 2. Print it; ask the user to confirm or correct. 3. Ask explicitly: license, optional add-ons, profile-specific questions. 4. Write the scaffold using `templates/`. Skip files that already exist. 5. Generate `BOOTSTRAP-MANIFEST.md` and `.bootstrap-meta.yaml`. 6. Print the "next 30 minutes" punch list. The skill is **same-session only**. If invoked cold (no prior design conversation in this session), refuse with a message asking the user to either have the design conversation first or paste a summary. The skill **never writes outside the project root** and **never clobbers existing files**. ## Stack profiles - `python-only`, `node-only`, `python+node`, `go-only`, `rust-only`, `polyglot` - `nix-flake` — NixOS-based projects; see [`patterns/appliance-nixos.md`](./patterns/appliance-nixos.md). - `none-yet` — stack-agnostic scaffold. ## Deploy models - `docker-compose` — standard service stack. - `single-binary` — one process, one binary. - `artifacts` — OS images, appliance models, anything where the deliverable is one or more built artifacts plus a config repo. - `library` — `docs/PUBLISH.md` instead of `docs/DEPLOY.md`. - `none-yet`. For background on w