Claude Code
Claude Code is a coding helper that can read a project, make changes, run tests and explain what it did, while you stay in charge.
Your terminal
Chapter 7 at a glance
7.1 What is Claude Code?
🎯 Goal: understand an AI coding helper- Claude Code helps people write, fix and understand code in a project.
- It can read the files in a project, edit them, run commands and tests and explain.
- People use it in a terminal and in other places such as desktop or web apps.
- It is a tool for builders. You still need to understand what you build.
💬 Chat vs 💻 Claude Code
🌍 Real-life examples
Too big.
Small and clear.
📝 Quick quiz
1. What can Claude Code do?
✅ Read, edit and test code in a project and explain it.
2. Where is it used?A) Terminal and other apps B) Only on phones
✅ A. It works in a terminal and other places.
3. Do you still need to understand the code?
✅ Yes.
7.2 Plan, edit, test, review
🎯 Goal: follow a safe coding loop- Plan first: ask what it will change before it changes.
- Edit small: one change at a time.
- Test: run the game or tests to see if it works.
- Review: read the changes. You decide to keep or undo.
🔁 The coding loop
🌍 Real-life examples
Hard to review.
Safe.
📝 Quick quiz
1. What comes first?
✅ Plan.
2. How big should each change be?A) Small B) Huge
✅ A. Small changes are easier to review.
3. Who decides to keep it?
✅ You.
7.3 Project memory and rules
🎯 Goal: give a project lasting instructions- A project can have a notes file, such as CLAUDE.md, with rules and facts Claude should always follow.
- Include: what the project is, how to run it and style rules.
- Add safety rules: never touch private files, never delete without asking.
- Keep it short and clear.
📜 A tiny CLAUDE.md
– Plain HTML, CSS and JavaScript
– Test by opening index.html
– Ask before deleting anything
– Keep code simple, add comments
🌍 Real-life examples
Easy to forget.
Always followed.
📝 Quick quiz
1. What goes in a project notes file?
✅ What it is, how to run it and rules.
2. Should safety rules be included?A) Yes B) No
✅ A. Yes.
3. How long should it be?
✅ Short and clear.
7.4 Coding safely
🎯 Goal: use coding tools responsibly- Practise on your own small projects only.
- Use version history or backups so you can undo.
- Read what it wants to run or change before you approve.
- Never put passwords or private data in code. Ask a grown-up to help with accounts and installs.
🛡️ Coding safety checklist
🌍 Real-life examples
Risky.
Safe.
📝 Quick quiz
1. What should you do before approving?
✅ Read what it wants to run or change.
2. Where to practise?A) A small practice project B) A school account
✅ A. Keep it small and separate.
3. Passwords in code?
✅ Never.
⌨️ Code Coach: Put the Steps in Order
Tap the steps in the right order. 3 rounds!
Chapter 7 summary
What Claude Code is • Plan, edit, test, review • Project rules • Coding safely.