ai-project-bootstrap
v1.0.0
Signed out
Some pages show more once you sign in — your licence key, your usage, and what the subscription covers.
Getting started
What this isInstallationThe wizard, question by questionYour first project
Choosing a stack
Describing your idea (Pro)Licensing & open sourcePresetsArchetypesPreset or archetype?Cost estimation
Technology catalogue
Browse all 35 modulesCategories & selection rulesSupabase
CLI reference
generateaddimplementreviewanalyzeupgradedoctorGlobal flags & exit codes
The generated project
File-by-file contractAI rules per toolRegenerating safelyai-project.config.json
Contributing
Adding a technologyAdding an implement providerAdding an archetypeAdding pricing dataChanging the engine
Docs / CLI reference / doctor

doctor

Checks whether this machine can actually build what you are about to generate — before you spend a wizard run finding out the hard way.

npx ai-project-bootstrap doctor              # Node, Git, npm, Bun — always
npx ai-project-bootstrap doctor --mobile     # + Xcode, Android SDK, Watchman, Java
npx ai-project-bootstrap doctor --backend    # + Docker
npx ai-project-bootstrap doctor --all
npx ai-project-bootstrap doctor --for startup-mvp

What affects the exit code

Node, Git and npm only. Everything else — Bun, Xcode, Android SDK, Watchman, Java, Docker — is informational, since this machine may simply not be the one you use for that platform.

Interactive vs. not

With no flags an interactive terminal is asked which extra tooling to check. A non-interactive one — CI, a pipe — runs the universal checks only.

Two different doctors

This one checks the machine, before anything has been generated. The `npm run doctor` a generated project ships with checks that project's own .env and setup.

Previous
upgrade
Next
Global flags & exit codes
On this page
What affects the exit codeInteractive vs. not
Source: README.md — Checking your environment