Claude Code
Your AI pair programmer — not just a chat tool but an agent that reads your code, writes files, runs commands, and ships features alongside you.
You have spent three sessions building the foundation:
- Session 1 — You commanded the machine directly. Code is instructions; the command line is the fast door to the OS.
- Session 2 — You understood what AI actually is: a probability engine, not magic. You know how it produces answers and why better context produces better results.
- Session 3 — You set up your toolkit: VS Code to write in, Git to track changes, GitHub to store and share, Supabase for your database, Vercel to publish live.
Now everything comes together.
Claude Code is the tool that sits at the centre of everything you will build from here. It is not a chatbot you copy-paste from. It is an agent that lives inside your project — reading your files, understanding your codebase, writing real code, running terminal commands, and shipping working features.
What Claude Code Actually Does
| What you type | What Claude Code does |
|---|---|
| "Add a column for payment status to the fees table" | Writes the Supabase migration file, updates the TypeScript types, updates the component — in one go |
| "The contact form is not sending emails" | Reads your edge function code, identifies the bug, proposes a fix, applies it |
| "Build the student enrolment page" | Scaffolds the page, form, validation, API call, and Supabase insert — naming files correctly for your project structure |
| "Run a type check and fix any errors" | Runs npx tsc --noEmit, reads the errors, edits the affected files |
The key shift: Claude Code acts — it does not just suggest. You review, approve, and push. But the doing is largely handled.
Why Session 4 and Not Earlier
You needed Sessions 1–3 first because Claude Code is most powerful when you understand:
- What the command line is — Claude Code uses a terminal. You now know what that is.
- How AI produces answers — You know why prompt quality matters and why the AI can be wrong. That makes you a better reviewer.
- What Git, GitHub, VS Code, Supabase, and Vercel do — Claude Code works with all of these. When it writes a migration or pushes to a branch, you now know exactly what it did.
A CA who understands the tools will catch errors. One who does not will blindly approve them. Session 4 is about using Claude Code with competence — not just speed.