bootstrap

name	bootstrap
description	New project scaffolding orchestrator that sets up a complete project from scratch with the right stack, structure, configuration, and initial code.
layer	orchestrator
category	orchestration
triggers	["/bootstrap","bootstrap a new project","scaffold a new app","start a new project","create a new project","init project"]
inputs	["Project type or description (e.g., \"Next.js SaaS app\", \"CLI tool in Rust\")","Optional tech stack preferences","Optional feature requirements","Optional deployment target"]
outputs	["Complete project directory structure","Configuration files (package.json, tsconfig, eslint, etc.)","Initial source code with example components or modules","Development tooling setup (linting, formatting, testing)","Git repository initialized with first commit","README with setup instructions"]
linksTo	["plan","research","scout","brainstorm","sequential-thinking","git-workflow","commit-crafter","docs-writer","mermaid"]
linkedFrom	["team"]
preferredNextSkills	["cook","team","kanban"]
fallbackSkills	["plan","research"]
riskLevel	low
memoryReadPolicy	selective
memoryWritePolicy	always
sideEffects	["Creates new directory structure","Creates configuration files","Creates initial source files","Initializes git repository","May install dependencies (npm install, cargo build, etc.)","Creates initial git commit"]

Bootstrap

Purpose

Bootstrap is the new project scaffolding orchestrator. It takes a project idea or specification and produces a complete, ready-to-develop project with the right directory structure, configuration, tooling, and initial code. Bootstrap doesn't just run create-next-app -- it makes informed decisions about project architecture, sets up quality tooling, and creates a foundation that follows best practices.

Bootstrap is opinionated but configurable. It will suggest a stack and structure based on the project type, but defers to user preferences when specified. It always errs on the side of a clean, maintainable foundation over a feature-packed but messy one.

Workflow

Phase 1: Discover & Decide

1. Parse the project brief -- Extract project type, target platform, scale expectations, and any specified technologies.
2. Invoke brainstorm (if underspecified) -- If the user gives a vague brief ("build me a SaaS"), brainstorm what the stack and structure should look like.
3. Invoke research -- Look up current best practices for the chosen stack. Check for latest versions, recommended configurations, and known pitfalls via Context7.
4. Invoke plan -- Create a scaffolding plan:
   • Directory structure
   • Configuration files needed
   • Dependencies (with versions)
   • Initial code files
   • Tooling (linter, formatter, test runner, CI)
5. Present the plan -- Show the user what will be created. Get confirmation before writing files.

Phase 2: Scaffold Structure

6. Create directory tree -- Build out the full directory structure following conventions for the chosen stack.
7. Write configuration files -- Generate all config files:
   • Package manager config (package.json, Cargo.toml, pyproject.toml, etc.)
   • TypeScript/language config (tsconfig.json, etc.)
   • Linter config (eslint, clippy, ruff, etc.)
   • Formatter config (prettier, rustfmt, black, etc.)
   • Test config (jest, vitest, pytest, etc.)
   • Git config (.gitignore, .gitattributes)
   • Editor config (.editorconfig, .vscode/settings.json)
   • Environment config (.env.example)

Phase 3: Write Initial Code

8. Create entry points -- Set up the main entry file(s) for the application.
9. Create example components/modules -- Write 1-2 example components or modules that demonstrate the project's conventions: