From Idea
to Product.
Yesterday you built pages people can see. Today you give your app a memory, a lock on the door, and a real product around it — and you ship it.
Day 2 at a glance.
A clear arc: in the morning you design and build the pieces. After lunch you join them into one product, test it, and present it.
By 5pm, you walk out with four things.
Not slides about a product. The product itself — built, secured, and live on the internet.
Yesterday the face. Today the brain.
Day 1 you built pages people can look at. They're real, they're live — but they forget everything the moment you refresh. Today we fix that.
From your laptop to a live link.
Your code doesn't magically appear online. It travels down a little assembly line — and today we add the last piece at the bottom.
GitHub is your project's time machine.
Think of the save points in a video game. Every time you save, you can always go back if something goes wrong. GitHub does that for your whole project — automatically, forever.
The GitHub workflow.
Read it like a map. The main line is your real project. You branch off to try something safely, then merge it back when it works.
Save it once. It ships itself.
This is CI/CD — a fancy term for one simple promise: the moment you save to GitHub, your site rebuilds and goes live on its own. No "uploading", no buttons.
Skills give it know-how. MCPs give it hands.
Today Claude isn't just chatting. It has expert playbooks loaded in its head, and live connections to real tools it can actually operate.
Nine helpers, one day.
You'll meet each one when you need it. Here's the whole team so nothing feels like a surprise.
Define Your
Product
Before you build anything, get crystal clear on what it is and who it's for. Three quick skills do the heavy lifting — you just answer honestly.
You wouldn't build a house without a blueprint.
Skip this and the AI guesses — you get a generic app for no one. Answer three questions and you get a builder brief you'll reuse all day.
Run the three skills in order
Build the
Landing Page
If you can't explain your product in one sentence, you can't build it either. So we write that sentence first — as the page that sells it.
Four parts. Copy before colour.
A passer-by decides in seconds. Every strong landing page answers four things — write the words first, make it pretty second.
not 30 emails.
Write → style → go live
Quick break.
You've got a brief, a validated idea, a design direction, and a landing page with a moving hero. Stretch — the fun part is next.
Build the
Prototype
Don't design the filing cabinet before you know what you're filing. First build the journey through your app — the data comes after.
The test drive before the engine.
A prototype is your app with the screens connected but no real data yet. You click through it to feel the journey — fix the path before you build the plumbing.
Build the skeleton
You know where to click. A stranger doesn't.
Testing your own app is the least reliable test — you skip the confusing bits without noticing. Playwright is a robot that opens your app fresh and tries to use it, then tells you what broke.
Build the
Database
Your flows work. Now give your app a memory that supports exactly those flows — and a lock so each person only sees their own data.
A filing cabinet with a lock.
A database is just a tidy filing cabinet for your app's data. You don't write any code — you name the things you store, and Supabase MCP builds the cabinet for you.
Plan it → let Claude build it
Your idea now has infrastructure.
This morning it was a sentence. Now it has a real, secured database behind it. Post it on the wall:
do [what]. Database: done."
Lunch.
You're walking in with a live landing page, a working prototype, and a secured database. The hard thinking is done — this afternoon you just connect the pieces.
Build the
Full App
Prototype, database, landing page — all built. Now you join them into one real product where the data actually saves.
Connect · complete · polish
You're not rebuilding — you're wiring your prototype to your real database, then filling in the screens you skipped.
One last check before you present.
Same robot as this morning, now testing the real thing — including the lock. You're looking for one answer: can a brand-new user get all the way through?
Showcase
Don't show them your app. Show them the problem it solves — then let the app prove it.
Tell a tiny story.
Not a feature tour. A before, a moment, and an after.
An idea this morning.
A product tonight.
Remember that fear you wrote at 9am? Read it again. You answered it — not because AI did the work, but because you showed up with a real problem and shipped the answer.
AI is your co-pilot, not your replacement.