Vibe coding is fast until it breaks: code nobody understands, a project you cannot change safely. Blueprint runs focused skills that plan, build, and prove one feature at a time, turning every decision into durable state you can inspect.
AI Blueprint 1.10.0 adds a compact sun and moon theme control to the local dashboard, follows the system theme on first use, and remembers an explicit choice across projects.
Starting fresh? Scaffold an app in your preferred stack first. Already have a working codebase? Install Blueprint inside it and use the adoption path.
Create the app in your preferred stack, then install Blueprint and tune the workflow to the new repo.
Blueprint surveys shipped features and existing conventions, then generates plans that reflect the real project.
The setup creates durable project context. Then every feature moves through a spec, implementation, proof, and review cycle.
Give the agent a durable understanding of what you are building.
One scoped feature moves through visible human review gates.
You own the plan. Blueprint turns it into durable context, one active feature, and a readable history of what shipped.
Clear the chat or come back next week and the next session resumes from those files, not from a conversation it no longer has.
Open a live, read-only view of the roadmap, current work, findings, configuration, Git state, and the next action. It refreshes from the same files Blueprint already uses and stays on your machine.
See what is complete, what comes next, and how much remains.
Catch warnings, findings, changed files, and branch state.
Return after a break and know exactly what moves the project forward.
$ blueprint dashboardExplore the dashboard →AI projects drift when scope, decisions, and proof live only in chat.
Blueprint is an AI coding workflow framework, not an application framework. Your stack, architecture, and product choices stay yours.
The agent writes the feature spec first, then stops. You approve the shape before code exists.
Plans, current work, standards, and history live beside the project in readable markdown.
The agent shows diffs, runs the real app, and proves each done-when before work lands.
Find the command for your task, including browser tests and manual guides.
Write the next spec
Build the approved spec
Verify behavior or generate a guide
Archive and close out
Think through an idea
Preview a planned feature
See progress and next steps
Diagnose a failure
Review code and risks
Check Blueprint setup
Tune a fresh scaffold
Survey existing code
Develop project plans
Generate project context
Explore the visual direction
Set up unit or browser tests
Automate project checks
Spec an unplanned change
Plan a safe reversal
Prepare deployment readiness
Build one bounded work item
Complete planned features serially
Blueprint stays lightweight by default. Add unit testing when application logic appears, run the same Verify recipe locally and on GitHub, then prepare release checks when the project is ready to ship.
Add the stack-native test runner when you need it, then let Blueprint define one Verify command from the configured typecheck, tests, and build. GitHub Actions runs that exact recipe automatically.
Blueprint checks the build, start command, output directory, environment names, and health path. It can prepare local Render or Vercel configuration when the project needs it.
Blueprint does not compete with app starters or coding agents. It gives them durable context and clear review boundaries.
| Option | What it gives you | What is still missing |
|---|---|---|
| App boilerplate | Starter code and patterns | Your product plan and workflow history |
| Chat-only AI coding | Fast implementation | Durable project state |
| AI Blueprint | A file-backed workflow framework | App code is still yours to choose |
No. It installs workflow files and agent skills, not auth, billing, database code, or UI components. Scaffold the app you actually want first.
No. The project state lives in markdown. Adapters currently support Codex, Claude Code, GitHub Copilot, and OpenCode, and the workflow can be understood by other coding agents.
No. The core loop is feature, implement, check, and complete. Discovery, brief, debug, try, audit, tests, browser tests, CI, release, prototype, rollback, autopilot, and continuous are optional tools for specific situations.
Yes. Run the adopt workflow. It surveys the real repo and creates plans that account for features you have already shipped.
Install AI Blueprint inside the app you already scaffolded. Your code stays yours. Your workflow gets clearer.