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 / Getting started / Your first project

Your first project

A ten-minute path from an empty directory to an assistant that knows your stack.

1. Check the machine

npx ai-project-bootstrap doctor --for startup-mvp

Node, Git and npm are the only checks that affect the exit code. Everything else is informational — this machine may simply not be the one you build iOS on.

2. Generate

npx ai-project-bootstrap --preset startup-mvp

Review what the preset filled, answer anything it left open, and let it write. You will see a file count and a line like: Est. cost $51/mo (Supabase, Sentry) — 1 usage-based service not counted.

3. Read three files, in this order

→docs/setup.md — how to get the stack running locally, per technology.
→docs/architecture.md — the component diagram, a sign-in sequence diagram for your auth provider, and a starter ERD if you picked a database.
→docs/roadmap.md — a suggested build order for exactly this stack, grouped into weeks capped at three items.

4. Fill the environment

cp .env.example .env
npm run doctor      # inside the generated project — checks .env and setup

5. Hand the first feature to your assistant

npx ai-project-bootstrap implement authentication

This writes a plan, prompts and a checklist tailored to the auth provider your project actually selected, plus skeleton files. Open the generated prompt and give it to your assistant — it already has the rules files as context.

Commit before you generate again

Every regeneration preserves files you have edited by hand, but a clean git status makes the diff trivial to read.

Previous
The wizard, question by question
Next
Describing your idea (Pro)
On this page
1. Check the machine2. Generate3. Read three files, in this order4. Fill the environment5. Hand the first feature to your assistant
Source: net-new