Generating the First Version
Get AI to produce a working starting point.
Generating the First Version is a free Vibe Coding lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Vibe Coding learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Time to Build for Real
You have a buildable idea. Now comes the magic moment of vibe coding: you hand that idea to an AI and watch it produce a working first version — often in seconds.
In this lesson you'll learn how to feed your prompt to tools like v0, Bolt, Lovable, or Cursor, what to expect from the output, and how to react when version one isn't perfect (it usually isn't — and that's fine).
Pick Your Builder
Different tools, same idea: describe, generate, preview. Here's a quick map for your first build:
- v0 — great for generating polished UI from a prompt.
- Bolt / Lovable — describe a whole app, get a live, editable project in the browser.
- Replit — build and run in the browser, full coding environment with AI.
- Cursor / Claude Code — AI that writes files right in a real code editor.
For your very first app, a browser app-builder like Bolt or Lovable is the friendliest place to start.
Paste Your Prompt
Generating the first version is as simple as pasting your build prompt into the tool's chat box and hitting send. Use the full prompt you shaped in the last lesson — what it is, who uses it, what they do, and the vibe.
Here's a complete first-version prompt you could drop into Bolt or v0 right now.
Build a single web page "Daily Water Tracker".
The user can:
- See a big counter starting at 0
- Tap a "+1 Glass" button to add a glass
- Tap a "Reset" button to set it back to 0
- See a short encouraging message when they reach 8 glasses
Style: clean and modern, centered card, soft blue colors, big friendly buttons.
Keep it as one self-contained page.What 'First Version' Really Means
The first version is a starting point, not the finish line. AI gives you something that runs and roughly matches your words. It will get most of it right and a few things "off."
That's the whole vibe-coding loop: generate → look → ask for changes → repeat. Don't expect perfection on shot one. Expect something to react to, which is far faster than starting from a blank page.
Read the Result Before Reacting
When the AI finishes, resist the urge to immediately retype your whole prompt. First, actually look at what it made:
- Does the main thing work? (Does the button do anything?)
- Is the layout roughly right?
- What's missing or wrong compared to your prompt?
This quick review tells you exactly what to ask for next — which you'll learn in lesson 3. For now, generating and seeing output is the win.
A Look at What Got Generated
From the water-tracker prompt, the AI writes the logic for you. You won't type this — but seeing it builds your confidence about what your words become.
Run this to watch the counter logic in action, exactly the kind of code AI produces from your prompt.
let glasses = 0;
const goal = 8;
function addGlass() {
glasses += 1;
if (glasses >= goal) return glasses + " glasses — goal reached! Great job!";
return glasses + " glasses so far. Keep going!";
}
function reset() { glasses = 0; return "Reset to 0."; }
console.log(addGlass());
console.log(addGlass());
for (let i = 0; i < 6; i++) addGlass();
console.log(addGlass());When the First Version Looks Wrong
Sometimes the AI misreads you. The counter starts at the wrong number, the colors are off, or a button is missing. This is normal and easy to fix.
Don't scrap everything. Note the gap between what you wanted and what you got — that gap is your next instruction. A first version that's 70% right is a great first version.
What I wanted: counter starts at 0, blue theme, two buttons.
What I got: counter starts at 1, gray theme, only +1 button.
Next instruction will simply close those gaps. No restart needed.If It Won't Run At All
Occasionally the first version errors out or shows a blank screen. Don't panic — and don't try to read the error yourself yet. Just tell the AI plainly.
Most builder tools let you paste the error or click "Fix" and the AI repairs its own code. You'll go deep on this in the Debugging course later.
The app shows a blank white screen and nothing happens when I click the button.
Here's the error from the console:
[paste the red error text here]
Please fix it so the button adds 1 to the counter, and tell me in one line what was wrong.Generate Variations to Explore
A superpower of AI builders: you can ask for several versions at once to explore options before committing. Great for design when you're not sure what you want.
This turns the first version into a menu instead of a single guess.
Generate 3 different visual styles for this water tracker:
1. Calm pastel and minimal
2. Bold and colorful with big rounded buttons
3. Dark mode with neon accents
Keep the same features in all three. I'll pick one to continue with.Keep What Works
Once you have a first version you like, lock it in before changing things. In browser builders, this might mean saving a version or noting the current state.
This way, if a later change breaks something, you can return to a known-good point. Vibe coding moves fast — having a save point keeps fast from becoming reckless.
Your First-Version Checklist
Before you call the first version done enough to start tweaking, run this quick checklist:
- The page loads without errors.
- The main action works (the key button does something).
- The layout is roughly what you described.
- You know the 1-3 things you want to change next.
Check those off and you're ready for the next lesson: asking for changes by chatting.
Quick Check
Your AI builder produced a first version that works but has the wrong colors and is missing one button. What's the best next move?
Recap: You Generated Version One
You learned how to turn your prompt into a real, running first version. Remember:
- Paste your full prompt into a builder like Bolt, Lovable, v0, or Replit.
- The first version is a starting point — expect ~70% right.
- Review before reacting: note what works and what's off.
- If it breaks, paste the error and let the AI fix itself.
- Save a good version before making big changes.
Next: shaping that first version into exactly what you want — just by chatting.
Frequently asked questions
Is the “Generating the First Version” lesson free?
Yes — the full text of “Generating the First Version” is free to read here on the web, and the Vibe Coding course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Vibe Coding course, upgrade to CoddyKit PRO.
What will I learn in “Generating the First Version”?
Get AI to produce a working starting point. You practise Vibe Coding with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Vibe Coding?
No prior experience is required. Vibe Coding on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Generating the First Version” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Vibe Coding lesson?
Yes. Every Vibe Coding lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Describing Your Idea
- Generating the First Version
- Asking for Changes
- Previewing and Running It