Build v1 With an AI App Builder

Why it matters

This is the lesson where your idea stops being a document and starts being a thing you can click. That jump is the whole point of building with AI: you do not need to learn to code for months before you can test whether people want what you are making. You describe it, an AI builder writes it, and you see it running in front of you the same day.

Your job today is not to make it beautiful. It is to make the one core action from your spec actually work, end to end, without you faking it or skipping steps. If your spec says a user signs up and gets a recommendation, that recommendation has to actually appear — not a placeholder, not “coming soon.”

Expect this to feel messy. AI builders are fast, but they misunderstand you sometimes, generate something close but not quite right, or break something that worked a minute ago. That is normal, and it is exactly what the next lesson is about — getting unstuck. For today, your only job is to sit down, describe your spec clearly, and keep iterating until the core action works in the preview.

By the end of this session you should have something you can show someone: not perfect, not polished, but real. That screen recording is proof, to yourself as much as anyone, that you can build.

What to watch for

Build and deploy a full-stack app using Lovable (everything you need)

• Watch for how specific and structured the prompts are — the builder responds better to clear instructions than to vague wishes.
• Notice the back-and-forth: build a piece, look at the result, correct it, and repeat, instead of writing one giant prompt and hoping.
• Skip memorizing the exact feature list shown; the pattern of describe, check, correct is what transfers to your own idea.

Start with Claude

Use Claude alongside your builder as a second set of eyes: to sharpen your prompts before you send them, and to help you think through what “done” looks like for your core action. Do not paste your whole idea and ask Claude to build it — that is the builder’s job.

I'm building v1 of my product in an AI app builder for the Make stage of Make First. My core action is: [paste from your spec]. I'm about to write my first prompt to the builder.

Help me sharpen my prompt before I send it — ask what the user sees first, what happens when they do the core action, and what "working" specifically looks like, so the builder has something precise to build. Don't write the app code yourself. After I paste back what the builder produced, help me spot what's missing or wrong compared to my spec, and help me write the next prompt to fix just that one thing.