Lesson 3: Talking to Claude Code
Fast-track: Already have Node.js and Git installed, know how to cycle permission modes with Shift+Tab, and write specific prompts? Skip to Lesson 4.
The three modes
Claude Code has three main permission modes. Cycle through them by pressing Shift+Tab:
| Mode | What it does | When to use it |
|---|---|---|
| Default | Claude Code asks permission before running commands or writing files | Normal usage — you review each action |
| Auto-accept edits | Claude Code can write and edit files without asking, but still asks before running commands | When you trust the code changes but want to approve commands |
| Plan mode | Claude Code only thinks and plans — no code, no commands | At the start of a project or when brainstorming |
Start every new project in plan mode. Here's why: Claude Code is eager. It wants to help. If you describe a project in default mode, it might immediately start writing code before you've agreed on the approach.
Plan mode is like telling Claude Code: "Please don't write code yet. Let's think first."
Yes — there are additional modes you can explore later as you get more comfortable. For now, these three are all you need.
The Magic Lamp Rule
This is the single most important concept in this entire course.
Treat Claude Code like a magic lamp. If you rub the lamp and say "I want to be a millionaire," the genie might make you rich — but doing something you hate. The wish was too vague.
The same applies to Claude Code:
| Vague (risky) | Specific (better) |
|---|---|
| "Help me authenticate users" | "Build a login form with email and password using Supabase Auth" |
| "Make the app look better" | "Add a dark header with the logo on the left and navigation links on the right" |
| "Fix the bug" | "The submit button on the payment form doesn't respond when clicked — investigate and fix" |
Be specific with your ask. Tell Claude Code what you want, where you want it, and how it should behave. The more precise your request, the better the result.
When starting a brand new project, it's okay to be broader — "I want to build a golf group management app" — because the whole point is for Claude Code to help you figure out the details. But once you're making changes to existing code, precision matters.
Essential commands
Keep this table handy. You'll use these constantly:
| Key / Command | What it does |
|---|---|
Escape | Interrupt Claude Code while it's working (it stops mid-action) |
Ctrl+C | Harder interrupt — if Claude Code is generating, it stops immediately. If you're at the input prompt, it exits Claude Code |
Escape twice | Clear your current input |
/clear | Start a fresh conversation (clears all context) |
/model | Switch AI models (you'll mostly use the default — explore this later) |
/mcp | View your connected MCP servers (more on this in Module 3) |
claude --continue | Continue your most recent conversation after closing the terminal |
claude --resume | Pick from a list of recent conversations to resume |
When to use /clear
Every conversation is a session. Claude Code remembers everything from the current session — your project description, the plan, the code it wrote, your feedback.
If you want to start completely fresh (new idea, new approach, or things got messy), use /clear. It wipes the conversation and gives you a clean slate.
When to use --continue and --resume
Closed your terminal by accident? Computer restarted? Run claude --continue:
claude --continue
This picks up your most recent conversation right where you left off. All the context — the plan, the code, your feedback — is still there. You can also use the short form: claude -c.
If you want to resume a specific older conversation (not necessarily the most recent one), use claude --resume — it shows you a list of recent sessions to pick from.
Language tip
Claude Code understands any language. But English tends to get the best results for technical work.
Why? The AI models have more English training data than any other language, and technical terms are more precise in English. The gap has narrowed with newer models, but it's still there.
You can mix languages if that's more natural for you. But for the prompts where precision matters (describing features, filing bugs, defining architecture), English will give you an edge.
Tokens: your conversation budget
Every message you send and every response Claude Code generates costs tokens — the units AI models use to measure text. Think of tokens as the currency of the conversation. Your Pro plan has a usage limit that resets automatically. You can check your remaining usage at claude.ai/settings.
Don't stress about tokens. At the start, just build. If you hit a limit, wait for it to reset or upgrade your plan.
The tool that builds itself
Here's something that will bend your brain a little: Claude Code can modify itself.
See that status bar at the bottom of your terminal? By default it shows basic info like your current model. But you can ask Claude Code to change it to whatever you want — a cost counter, a project name, a motivational quote. Try it:
Can you change the status bar at the bottom of Claude Code to show the conversation cost so far?
Claude Code will edit its own configuration and the status bar updates. This isn't a gimmick — it's your first glimpse of a core idea in this course: the tool builds the tool. Claude Code is software, and it can modify software. Including itself.
You'll use this principle constantly. Need a custom workflow? Ask Claude Code to build it. Want a shortcut for something repetitive? Ask Claude Code to set it up. The barrier between "using a tool" and "building a tool" disappears.
Claude Code will let you know when you've reached your limit. Your work is saved — all the code Claude Code wrote is still on your computer.
When your limit resets (check your settings page for the countdown), run claude --continue to pick up where you left off. All the context — the plan, the code, your feedback — is still there.
Your first real task: set up your dev tools
You've learned how to talk to Claude Code. Now let's put it to work. The apps you build in this course need two tools installed on your computer:
- Node.js — the engine that runs your app's code
- Git — a save-point system for your project (like saving your progress in a game — you can always go back)
Claude Code on Windows needs Git to work properly, so you'll need to install it before using Claude Code for the rest. Go to git-scm.com, download the installer, and click "Next" through all the screens — the defaults are fine. Then close and reopen your terminal and run claude again.
Once Git is installed, Claude Code can help you with everything else.
Instead of following a step-by-step installation guide, just ask Claude Code to help. Type this directly into your Claude Code session:
On Mac:
I need to install Node.js and Git on my computer. Can you help me set them up? I'm on Mac.
On Windows (after installing Git above):
I need to install Node.js on my computer. Can you help me set it up? I'm on Windows.
Claude Code will walk you through each installation — what to download, what to click, and how to verify everything works. If something goes wrong, Claude Code is right there to troubleshoot.
Important: After installing a tool, you'll need to close and reopen your terminal so it can see the newly installed programs. Then run claude again to get back into Claude Code.
Verify your setup
Once you're back in Claude Code after the installs, ask it to verify:
Can you check if Node.js and Git are properly installed on my computer? Run the version checks.
Claude Code will run node --version, npm --version, and git --version for you. You should see version numbers for all three. If something's not working, Claude Code will help you fix it right there — no copy-pasting prompts into a separate chatbot needed.
When you install Node.js, you also get npm (Node Package Manager). It's the tool that installs JavaScript packages — think of it like an app store for code libraries. You'll use it to install the building blocks for your app. You don't need to learn npm commands — Claude Code handles them for you.
When you install Git on Windows, you'll also get Git Bash — an alternative terminal that uses the same commands as Mac. This makes it easier to follow along with the course. To open it: right-click your desktop, choose "Show more options" if you're on Windows 11, then click "Git Bash Here."
You can use PowerShell or Git Bash — either works for this course.
Checkpoint
You're ready for the next lesson if:
- You can cycle through the three modes with Shift+Tab
- You understand why plan mode comes first
- You can explain the Magic Lamp Rule in your own words
- You know how to interrupt Claude Code (
Escape), clear a session (/clear), and resume (claude --continue) - Node.js is installed (
node --versionshows 18 or higher) - Git is installed (
git --versionshows a version number) - You've used Claude Code to help you with a real task