Start Here · 02 / 07
Vibe 101 Session Flow
The 3-hour SDD Website Build Lab map, with timeboxes and the output you finish each stage with.
Vibe 101 / Current checkpoint
Session Flow
Ready to stamp - Saved in this browser only.
0 of 7 checkpoints complete.
Vibe 101 Session Flow
What this is
This is the 3-hour map for the SDD Website Build Lab. You use the Vibe SDD Starter Pack in Website mode and move through one saved stage at a time:
Setup Gate -> Website mode -> Project Brief -> Design Direction -> Build Blueprint -> Work Cards -> First Visible Build -> Review/Fix -> ProofWhy it matters
The session moves fast, so each stage needs a clear output. Saved files protect the plan, and Work Cards keep implementation small enough to check and explain.
Aim for one of these success levels:
Minimum: SDD planning files + first visible website or screenshot + 60-second explanation.
Good: minimum + one Review Mirror fix.
Strong: a GitHub and Vercel URL when time and accounts allow.What to do
Follow this timeboxed agenda:
| Time | Stage | What you finish with |
|---|---|---|
| 0:00-0:15 | Open the Starter Pack | Website mode chosen |
| 0:15-0:30 | Setup Gate | Tools, accounts, and folder ready |
| 0:30-0:50 | Choose your website project | One small, locked idea |
| 0:50-1:15 | Project Brief via the Blueprint Coach | project-brief.md saved |
| 1:15-1:35 | Design Direction | DesignMD inspiration translated into design.md |
| 1:35-1:55 | Design + Build Blueprint | build-blueprint.md, build-status.md, and first card saved |
| 1:55-2:30 | First Visible Build | First visible website section |
| 2:30-2:45 | Review + Finish | One checked fix against brief and design |
| 2:45-3:00 | Capture proof | Screenshot or URL plus 60-second story |
Keep the whole build inside the shared Vibe SDD files. If a chat or credit limit interrupts you, build-status.md tells the next session exactly where to continue.
Common mistakes
- Starting the build before the Setup Gate and planning files are complete.
- Trying to implement several Work Cards at once.
- Letting AI skip explanations or verification.
- Treating deployment as the only valid finish.