Skim before Session 1. Keep open during sessions.
Environment: Windows 11 laptops, PowerShell via Windows Terminal, python on PATH.
All commands below assume that.
claude doesn’t start / hangsclaude prompts for a loginRun this on one lab machine:
python --version # should print 3.x
python -c "import tkinter" # must produce no output
claude # should launch and accept a prompt
No git check needed — campers don’t use git. Save points are folder copies; see “Save Point / Undo Problems” below.
&& does not work in PowerShell 5.1. Lab machines may run 5.1 or 7, and there’s
no reliable way to tell which from the outside — so write and teach every command
one-per-line regardless of version. That syntax works on both.$HOME\Documents\Projects, not ~/Documents/Projects.
/ often works anyway, but the AI may generate either; both are fine in Python.python file.py), but if you hit it: Get-ExecutionPolicy to check.python with no arguments on some Windows setups opens the Microsoft Store instead
of Python. If that happens, Python isn’t properly installed on that image — swap the
machine, don’t debug it during class.claude doesn’t start / hangsCtrl+C, run claude again — fixes most of themclaude prompts for a loginclaude is the one command on every machine. If it asks to log in, that machine isn’t
signed in — get every machine signed in during “Before Campers Arrive,” and if one
still prompts, move the camper to a machine that’s signed in. Don’t debug logins in
front of the class.
Ctrl+C and rerun. If it happens across the whole room at once, that’s the API or the
network, not the campers — go analog for a few minutes (spec sheets, prompt lab,
partner pitches) and retry.
Real, and worth naming as a lesson: the conversation is full of stale context.
/clear
Code is untouched. If there’s a CLAUDE.md, the AI re-reads the project immediately.
Almost always started in the wrong folder.
Get-Location # where am I?
Get-ChildItem # is my file here?
Ctrl+C, cd to the right folder, claude again.
The conversation has locked onto a wrong theory. Escalate:
/clear, then describe the problem fresh — not the failed fixesSay the language and library in the prompt, or put it in CLAUDE.md:
## Rules
- Python 3 and tkinter only. No other libraries.
Explain once to the room: it’s asking before it changes files or runs commands. Read what it wants to do, then approve. Don’t teach campers to approve blindly — that’s the opposite of the whole curriculum.
ModuleNotFoundError: No module named 'tkinter'On Windows, tkinter ships with the standard python.org installer, so this means Python was installed without the “tcl/tk and IDLE” option ticked. Not a class-time fix — move the camper to another machine and reimage later.
python opens the Microsoft StoreWindows’ app-execution alias is intercepting it and real Python isn’t on PATH. Swap machines. Don’t fix this during a session.
root.mainloop() at the end. Tell the AI: “The window doesn’t appear when I
run it.”Same cause — missing mainloop(), or the script ends. Report it as a bug to the AI in
the standard format.
IndentationError after a camper hand-editsMixed tabs and spaces. Easiest fix: “There’s an indentation error on line 23, fix it.”
Campers don’t use git. Save points are folder copies — taught in Session 3, which is high school only. The reference commands:
cd $HOME\Documents\Projects
cd <Name>
Copy-Item -Recurse myproject myproject-working # SAVE
Remove-Item -Recurse myproject # UNDO (two steps)
Copy-Item -Recurse myproject-working myproject
<Name> is the camper’s name folder — each camper works inside their own, so
projects are Projects\<Name>\<project>.
Nothing to restore to. Hard lesson, teaches itself — but soften it and help them rebuild. Then have them make a copy immediately, and check on them again in ten minutes.
Remove-Item -Recurse asks for confirmationOn some setups it prompts per-item. Add -Force:
Remove-Item -Recurse -Force myproject
Only teach -Force when it comes up — it’s one more thing to explain, and it makes the
delete irreversible.
The app is still running, or Claude Code is open in that folder. Close the tkinter
window, Ctrl+C out of claude, then retry.
This is the most common failure in the restore cycle. Check it first.
Usually one of:
Copy-Item -Recurse SOURCE DESTINATION — source first. If they’ve destroyed the good
copy, check for an older one; campers often have several.Expected by mid-session. Have them name copies meaningfully — quiz-scoring-works, not
quiz2, quiz3, quiz4. Deleting old copies is fine once a newer one is confirmed
working.
Produces myproject\myproject-working\..., which confuses both the camper and the AI —
Claude Code will read the nested copy as part of the project. Make sure they cd
$HOME\Documents\Projects, then cd <Name>, so copies sit next to the project, not
inside it.
Worth showing on the projector once. It’s the mistake that generates the weirdest downstream symptoms.
Never “add more features.” Instead:
Allowed — if they already know it. Say yes and set two conditions:
Everything you’re teaching still applies unchanged — prompt sizing, the four checks, scope cutting, commits. Only the example code differs. A camper building in JS is getting the same curriculum.
Watch for the camper who picks an unfamiliar language because it sounds impressive. Ask: “have you written this before?” If no, steer to Python for today.
The failure mode this whole curriculum exists to prevent. Interrupt with:
“Show me what it just changed. What does this part do?”
If they can’t answer, that’s the teaching moment. Rule 4 exists for exactly this: you have to be able to explain what your app does.
Stop everything and demo the fix on the projector. Ten minutes of your time beats twenty-five campers burning ten minutes each.
Halt the room. Pick a camper’s app, put it on the projector, and break it in 30 seconds with empty input. This costs five minutes and resets the room’s behavior for the rest of the day.
Have this ready. It’s a real risk and it will happen at least once.
Analog activities that still teach the actual skills:
None of this is filler. Verification and scoping are the parts campers are worst at, and they don’t need a computer.
This Vibe Coding Curriculum by Brian Bird, created in with AI assistance, is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.