Build with a workflow you can inspect.
Set up Blueprint inside a project, give your coding agent durable context, and move each feature through a reviewed spec, implementation, proof, and finish.
Choose your starting point
Blueprint is added after the application exists. Pick the path that matches the real state of your codebase.
Scaffold first, then onboard.
Use this when the app is new or contains little more than framework boilerplate.
- Scaffold your app
- Install Blueprint
- Run /onboard
- Write two plans
- Run /overview
Adopt what already works.
Use this when the project already has meaningful features, architecture, and conventions.
- Install Blueprint
- Run /adopt
- Review generated plans
- Run /overview
- Enter the feature loop
Explore the system
Start with setup, then move into the workflow and reference material as the project grows.
Getting Started
What Blueprint installs, what it leaves alone, supported tools, and the shortest successful path.
Open guide →02 / BUILDCore Workflow
Spec, implement, check, and complete one feature at a time with visible review gates.
See the loop →03 / COMMANDSCommand Reference
When to use each skill, what it reads and writes, and the boundaries it will not cross.
Browse commands →04 / FILESFile Reference
Understand the two plans you own, generated context, active work, standards, and history.
View file map →05 / QUALITYTests and Review
Add unit testing, prove the real app, create a manual try guide, and run a quality audit.
Add quality gates →06 / SHIPRelease and Troubleshooting
Prepare Render or Vercel deployment, inspect workflow health, and recover from common issues.
Prepare to ship →