Module 6 · Learn to fly solo: troubleshooting & getting unstuck
How to get unstuck (the real skill)
Here’s the real goal of this whole course: not any single edit, but the ability to handle whatever comes up on your own. The good news — it comes down to one skill you already started practising in Module 1. Knowing how to get unstuck is what makes you independent.
Watch — hand-picked
The clearest walkthroughs of this step, from creators we rate. Each one’s credited — go give them a follow.
GitHub Basics Made Easy: A Fast Beginner's Tutorial!
The one skill: tell Claude what’s going on
Being stuck is normal — it happens to professionals every day. The difference is they know that the fix is almost always just giving Claude good context: what you were trying to do, what you did, and what happened instead. Do that, and Claude can untangle nearly anything.
The all-purpose 'I'm stuck' prompt
I'm stuck and I'm not technical, so please keep this simple. Here's the situation: - What I'm trying to do: [ what you wanted to happen ] - What I did: [ the last thing you tried ] - What happened instead: [ what you're seeing — copy any red text or error exactly, or describe it ] Please explain what's going on in plain English, tell me what to do next one step at a time, and handle any technical parts for me.
Keep this handy
We’ve put that prompt and a handful of others — for error messages, a preview that won’t open, a change that didn’t show up, a failed publish, and undoing things — into one cheat sheet. Keep it near your desk.
DownloadA few habits of people who never stay stuck
- Paste the exact error. Don’t summarize it — copy the whole message (or screenshot it). The details are what Claude needs.
- Say “I’m not technical, explain simply.” It changes how Claude talks to you. Use it freely.
- Ask “what are my options?” When you’re unsure, have Claude lay out the choices in plain English before you decide.
- Lean on undo. If something feels wrong, go back to a version that worked and try again. You can’t lose.
- One step at a time. Ask Claude to slow down and do things one at a time whenever it’s moving faster than you’d like.
If a lesson and its video and Claude’s help still haven’t cracked it, take a breath — it’s not you. Re-watch the module’s video, then give Claude the fullest description you can using the prompt above. And if Evolvv built your site, you can always reach out to us; but you’ll be surprised how rarely you’ll need to.
You have a reliable way to get unstuck — give Claude context, paste the error, ask for plain English — and a cheat sheet for the common moments. That’s independence.
Meta, but true: if you’re stuck on getting unstuck, just paste this: “I’m not sure how to describe my problem to you. Can you ask me a few simple questions to figure out what’s wrong and how to fix it?” Let Claude interview you.