Module 1 · Learn to drive: how to tell AI what to build
When things break (they will, and it's fine)
Things will break. A page won’t open, a change won’t stick, a red error message appears. This is completely normal — and the skill that fixes it isn’t being a genius, it’s staying calm and knowing the routine.
Breaking is the job, not a failure
Professional developers see errors all day, every day. An error isn’t a sign you did something wrong or that you’re not cut out for this. It’s just the computer saying “I got stuck here” — and it’s usually pointing right at the fix. You don’t need to understand it. You need to hand it to Claude.
The routine that fixes most problems
Whenever anything breaks, do the same three things:
- Copy the whole error. All of it — the entire red message, even if it looks like nonsense. Don’t summarize it; the details are what Claude needs.
- Paste it back into Claude. Into the same conversation you’re building in.
- Say the magic line. “I got this error — explain it in plain English and fix it.”
Claude reads the error, tells you in plain words what happened, and fixes it. Most problems end right here, on the first try. If you can’t copy the error — say it’s a blank page, or the button just does nothing — describe what you see instead: “the page is blank,” “nothing happens when I click save.” Plain English works.
The two magic sentences for when it’s stubborn
Occasionally the first fix doesn’t take. Two sentences get you out of almost every corner. When a fix isn’t working after a couple of tries:
When a fix isn’t landing
It's still not working — try a different approach.
This tells Claude to stop pushing on the same idea and come at the problem another way. And when things have gotten tangled and you want a clean slate:
When you want to reset
Go back to the last snapshot and let's try again.
This is why you save snapshots. A known-good version is always waiting behind you, so no experiment can ever really strand you.
If you’ve gone a few rounds and you’re getting frustrated, close it and come back later. A fresh session with fresh eyes solves problems that a tired hour couldn’t. Nothing is lost — your work and your snapshots are saved. Walking away is a technique, not a defeat.
Copy the error, paste it to Claude, ask it to explain and fix. If it’s stubborn: try a different approach, or go back to the last snapshot. That handful of moves covers nearly everything you’ll ever hit.
You’re now ready to build for real. Every build module ahead ends with its own “if you get stuck” help, tuned to that exact tool — so you’re never troubleshooting alone. Onward.
More learning resources
Still want another angle? These are hand-picked and vetted to line up with this lesson — from creators and sites worth your time.