What You'll Need Before You Start
A two-minute checklist — which tool to open, what a free account gets you, and the one trick that works when a button isn't where a lesson says it'll be.
🧰 What You Actually Need
Nothing to install. Nothing to configure. Just:
- A browser, on a computer or a phone
- A free account on one AI tool
- About ten minutes for your first build
That’s the whole list.
🔧 Pick One Tool
There are lots of tools that can vibe code, and new ones appear all the time. Rather than memorize a list, it helps to know the two types — because a tool of either type will work for this whole course:
| Type | What it is | Examples today |
|---|---|---|
| Conversational assistant | A general chat AI that also builds and previews small apps right in the conversation | Claude (claude.ai), Gemini (gemini.google.com) |
| Build-focused app tool | Purpose-built to go straight from a description to a running, hosted app | Replit, Lovable, Bolt, v0 |
If you don’t already have a preference, start with a conversational assistant — Claude or Gemini. Both are free, open in a browser, and need nothing installed, which makes them the smoothest place to feel the loop for the first time. You can always try a build-focused tool later.
The landscape shifts; your skills don’t. The specific names in that table will change — some will be renamed, replaced, or joined by tools that don’t exist yet. That’s fine. Everything you learn in this course is about directing an AI in plain language, and that transfers to whatever tool you’re sitting in front of. Don’t wait for the “best” one; pick any tool of either type and start.
A free account is enough for everything in this course. Free tiers do have limits — if a tool ever slows down, asks you to wait, or caps how much you can send in a day, that’s the free tier working as designed, not something you broke. Waiting it out or switching tools for that session both work fine.
🌐 Your Browser Is the Last Piece
Whichever tool you pick, your first builds in this course are web pages — usually a single HTML file. And the thing that runs an HTML file is something you already have open right now: a web browser (Chrome, Safari, Firefox, Edge — any of them).
Most tools show your app running right there in the chat or in a preview panel. But even in the simplest case, if a tool just hands you an HTML file, you can save it and double-click it — it opens in your browser and runs, no hosting or setup required. That’s the whole reason we start with a single HTML file: the tool builds it, and the browser you already have runs it.
| Piece | What it does |
|---|---|
| Your AI tool | Writes the HTML file from your description |
| Your browser | Opens that file and runs it as a working app |
So the real toolkit is just two things: an AI to build, and a browser to run.
🧭 The One Trick for When a Button Isn’t Where We Said
Every lesson in this course describes actions in plain language — “find the preview,” “look for a publish button” — because that’s genuinely all you need to know what to do. But these tools update their interfaces constantly, and no lesson can promise a button will be in the exact spot or have the exact label it has today.
If you’re ever looking for a button, tab, or menu a lesson describes and it isn’t where you expect, don’t hunt around guessing. Just ask, in the same chat:
“Where do I click to see this running?” or “How do I get a shareable link to this?”
The AI knows its own current interface better than any lesson written in advance ever could. This isn’t a workaround — it’s the same Directing skill Module 1 teaches, aimed at the tool itself instead of your app.
⏭️ Up Next
That’s everything. Module 1 starts with a celebration moment, then your very first build.