Claude Code Deep Dive
Permission modes · CLAUDE.md · costs · prompting
Block breakdown
What each session covers. Tier pills show when AI is off (A), foundation (B), or AI-default (C).
- A
A — Recap + Install
20 minEvery student has claude --version working by end of block.
- B C
B — Mental Model + Live Tool Exploration
15 minStudents can name the four concepts (Session, Context, Permission, Cost) and have seen /help, /usage, /clear live.
- C
C — First Real Session
27 minStudents have watched a complete Claude Code session -- file creation, edit approval/rejection/undo, running commands.
- B
D — Permission Modes + Planning Mode
25 minStudents understand the 4 primary permission modes, can switch between them, and know when to use each.
- B C
E — CLAUDE.md
25 minStudents have a CLAUDE.md in their project generated by /init and edited with at least one meaningful addition.
- A
F — Cost & Token Awareness
10 minStudents can check their session cost with /usage and have realistic expectations for small vs large projects.
- C
A — Recap + Common Issues
13 minStudents surface and resolve overnight issues; reconnect with session cost context.
- C
B — Vague vs Specific Prompting
30 minStudents can write a specific prompt and articulate why specific prompts produce better results -- plus when vague is actually better.
- C
C — Workflow Patterns
30 minStudents have tried at least one workflow pattern (Build, Refactor, Explain, Fix) on a real codebase.
- B
D — AI Struggle Signals + Session Management
25 minStudents can identify the 4 struggle signals and apply the right response strategy (re-prompt, manual intervention, /clear, /compact).
- C
E — Buddy Pair Exercise
15 minStudents have experienced prompting Claude Code collaboratively -- one typing, one directing -- and have a mini-feature to show.
- A
F — Wrap
5 minStudents know homework expectations, understand the idea submission deadline, and leave feeling capable.