bootstrap

Bootstrap — Auto-Configure Claude Code for Your Project

Work through each phase sequentially, asking the user for input only where marked.

---

Phase 0: Check for Setup Report

Before running detection, check if a /setup audit report exists earlier in this conversation. Look for a fenced code block with the setup-report language tag.

If found:

• Parse the stack, tools, category statuses, and suggestions
• Tell the user: "Found your /setup audit — focusing on the gaps it identified."
• Still run Phase 1 detection as normal, but use the setup report to enhance subsequent phases:
  • Prioritize categories marked IMPROVE or MISSING — generate config for these first
  • Skip prompting for categories marked GOOD — they're already configured
  • Use setup's suggestions as a checklist — ensure each one is addressed in the generated config
  • In Phase 8 summary, note which setup suggestions were applied

If not found:

• Proceed normally — this is the default path for standalone /bootstrap usage

---

Phase 1: Detect Project Stack

1.1 Read Project Metadata

Check for these files (in priority order):

• package.json (Node.js/JavaScript/TypeScript)
• pyproject.toml or setup.py (Python)
• Cargo.toml (Rust)
• go.mod (Go)
• pom.xml or build.gradle (Java/JVM)
• Gemfile (Ruby)
• composer.json (PHP)

1.2 Detect Tools

Package managers:

• Check for lockfiles: package-lock.json (npm), yarn.lock, pnpm-lock.yaml, bun.lockb, poetry.lock, Cargo.lock, go.sum, etc.

Formatters:

• .prettierrc, .prettierrc.json, prettier.config.js → Prettier
• pyproject.toml with [tool.black] → Black
• .rustfmt.toml → rustfmt
• .gofmt or standard Go project → gofmt
• .php-cs-fixer.php → PHP CS Fixer
• biome.json, biome.jsonc → Biome (format: biome format --write)

Linters:

• .eslintrc* → ESLint
• eslint.config.* → ESLint (flat config)
• biome.json, biome.jsonc → Biome (lint: biome check)
• pyproject.toml with [tool.ruff] or .ruff.toml → Ruff
• pylint.rc → Pylint
• clippy.toml → Clippy
• .golangci.yml → golangci-lint