Your first build (live demo loop)
Open the tool. Build. Iterate every 30 minutes.
The first prompt
Paste your spec into the tool. End with: 'Build this. Keep it minimal. Use the simplest possible stack. Deploy when done.' For Lovable/Bolt, the tool handles the rest. For Cursor, you'll see the code being written and need to confirm changes.
The 30-minute demo loop
Don't keep building for 4 hours before looking at the output. Every 30 minutes: open the live preview, click through the full user flow, note what's broken or missing. Then describe the fixes to the AI in plain English. Five short demos catch problems early; one big-bang demo at the end means costly rebuilds.
When things go wrong
Almost everything will go wrong the first time. The form won't submit, the buttons won't be styled, the deployment will fail. This is normal. The skill is in iterating: 'the booking form doesn't submit — fix it', 'the buttons look ugly, make them match this color scheme', 'the deployment failed — show me the error and fix it'. The AI fixes specific problems; vague complaints produce vague fixes.
1. How often should you preview your live build during a session?
Build the spec from lesson 3
Open your tool. Paste your one-page spec. Build. Preview every 30 minutes. Don't stop until you have a working URL someone could visit.
You have a public URL. The main flow works end-to-end. You used the live preview at least 3 times during the build.
Preview every 30 minutes during a build session — never go more than an hour without seeing the output.
Get the next course before anyone else
Subscribers get new courses a week early and a monthly rate-change report on the catalog.