Dev Environment Bootstrapper
One command to go from "fresh laptop" to "tests passing"
Standardize local setup to eliminate "works on my machine" issues. Generates a single bootstrap path (scripts, containers, env vars) and a smoke test to prove readiness.
INGREDIENTS
PROMPT
Create a skill called "Dev Environment Bootstrapper". Inputs: - Target repo and supported OSes - Current setup instructions (README) and CI workflow snippet (if available) Outputs: - A one-command bootstrap spec (make/task script steps) - A pinned toolchain plan (versions + where they're declared) - A smoke-test plan that mirrors CI as closely as practical - A .env.example template and secret-handling guidance for local dev Be strict about reproducibility and clear error messages.
How It Works
This recipe creates a deterministic local dev bootstrap: pinned tool versions, repeatable
dependency installs, and a minimal smoke test that mirrors CI.
Triggers
- Dev setup differs per person ("everyone has their own way")
- New hires spend days installing prerequisites
- Local works but CI fails (or vice versa)
Steps
- Define the canonical toolchain versions (runtime, package manager, build tool).
- Add a "bootstrap" command (Make/task runner/script) that:
- installs deps from lockfiles,
- creates a local config (.env.example),
- starts required services (or uses docker compose).
- Add a fast smoke test: build + one unit test + one "health" request.
- Fail loudly if prerequisites are missing; print exact fix commands.
- Run bootstrap in CI nightly to catch drift early.
Expected Outcome
- Fresh machines can run the project consistently.
- Setup failures become actionable (missing dependency, wrong version, bad env var).
Example Inputs
- "Turn our README setup into a single `make dev` flow."
- "We need Docker-based setup for macOS + Linux parity."
- "Make CI and local use the same build command and test flags."
Tips
- Prefer version pinning over "install latest."
- Make the smoke test fast enough to run on every change.