Your builder path
1 / 6 chaptersThis chapter
Step 1 of 6Your next action
Know what you are doing
Understand what building with AI really is
AI hands you a draft in seconds. It becomes proof only after you test the main action yourself. Read this step, then say the difference out loud.
Need a hand?
If it still feels abstract, look at the Draft, then decide diagram in this step. The middle box is the one people skip.
For this step
Core rule
Draft, then decide
AI hands you a draft in seconds. It becomes proof only after you test the main action and judge the result.
AI output
A draft, in seconds
You test and decide
Does the main action work?
Proof
Something you can explain
Skip the middle step and the build looks finished without being finished.
Role shift
Where the effort moved
The work did not disappear. It moved from typing syntax to describing, testing, and correcting.
Before AI
- Learn the syntax
- Type most of the code
- Search every error
With AI
- Describe the result
- AI drafts it
- You test and correct
Same thinking. The effort moved from typing to directing and checking.
The one-prompt myth says you describe an app and receive a working product. What you actually receive is something that looks like a working product.
| The one-prompt myth | What actually happens |
|---|---|
| One prompt builds the whole app | One prompt builds a convincing shell |
| The result is finished | The result is a first draft |
| Errors mean the AI failed | Errors are a normal part of building |
| You review it at the end | You review after every small piece |
AI changed how much typing a build takes. It did not change who is responsible for the result. The effort moved from typing to directing and checking.
Core rule
AI gives you a draft. You turn it into proof.
For this step
An editor is the program where your project files, your terminal and your AI helper all live in one window. You will not write much code by hand, but every command, every file and every preview passes through it.
| Editor | Pick it if |
|---|---|
| VS Code | The class default. Kilo Code installs here cleanly |
| Cursor | You already use it and know your way around |
| Antigravity | You already use it |
All three share the same layout and the same keyboard shortcuts, so every instruction in this path works in any of them. You do not need to choose an AI helper yet; the class installs one together in the next chapter.
For this step
Your KD account is where your finished build gets shown at the end of the path, and where session announcements land. Sign up with an email you actually check.
For this step
Registering is not a formality. It is what links you to today's session, and your profile has to be on that list before an API key can be allocated to it.
That key is how you get AI tokens for free during this session. It appears in your KD profile under the API Key tab, and you will connect it to your editor in the next chapter, with the trainer.
| What | Where |
|---|---|
| Today's session | The KD events page, named by your trainer |
| Your key, later | KD profile, API Key tab |
| Connecting it | Next chapter, with the trainer |
Register before you go further
Keys are allocated to registered profiles only. If you skip this and register later, you will be waiting while the room is building.
Not at a KD event? You can still do everything in this path. You will supply your own model key, or use a coding helper you already pay for, when you reach the next chapter.
For this step
GitHub stores a copy of your project away from your machine, and it is the account Vercel uses to publish it. Choose a username you are happy to show, because it appears in your project's public address.
If GitHub is blocked
A screenshot of your working build still counts as proof. Keep going and tell your trainer which step blocked you.
For this step
Vercel turns a GitHub repository into a live web address. Sign up with the Continue with GitHub button so the two accounts are linked before you reach the Share chapter.
| If this is blocked | Use instead |
|---|---|
| Vercel | GitHub link plus a screenshot |
| GitHub and Vercel | A short screen recording of the main action |
Before you move on
Common mistakes
- Installing a second editor because the first one looked unfamiliar.
- Skipping the event registration, then finding no API key waiting for you.
- Treating a polished first answer as a finished answer.
- Signing up to Vercel with a different account than GitHub, so the two never link.
- Losing build time to an optional account problem when screenshot proof is fine.
Work through one step at a time. Ticking a step marks it for this page view only, so nothing is saved when you leave.