Dec '25 • General discussion
🚨 How I’m shipping clean demos in <2 hours with AI (and why this matters for OXB)
Quick share on something that’s been working extremely well for me lately.
When I vibe code websites or landing pages in Cursor, I don’t give it one big prompt anymore. That almost always leads to shortcuts, weird simplifications, and painful debugging.
Instead, I use what I call a phased approach.
The idea is simple:
- break the build into phases
- force the AI to complete one small task at a time
- review each phase locally
- fix anything small
- type “continue” and move on
This does two big things:
- you get cleaner output
- if something breaks, you know exactly which phase caused it
It’s how I’ve been getting live, working demos up in under two hours, including the teaser page we’re building for OXB.
I recorded a quick walkthrough video explaining the approach and showing a real example: https://www.loom.com/share/1d8f7375ad5f423eb012f52c2e101606
In the comments, I’m dropping the exact prompt template I use, so you can:
- describe your idea in plain English
- paste the template under it
- generate a phased prompt you can drop straight into Cursor or any vibe coding tool
If you try it, post what you build. Would love to see how people in here use it.
1
1 comment
🚨 How I’m shipping clean demos in <2 hours with AI (and why this matters for OXB)
skool.com/oxb
A room where operators and builders get blunt feedback, better systems, and a curated studio that turns skills into clients, deals, and projects.
Powered by