Learn Claude Code, from searching a codebase to building agents
This free course has 18 chapters, and each one works through a problem
at an Indian company in drawings that change as you scroll. In chapter
1, Claude Code finds the one delivery rule that has to change in
Delhivery's codebase of about 1,800 files.
The chapters start with what you use on your first day, such as
searching code and giving Claude Code your team's rules. They end with
agents that work through long jobs on their own.
This page follows Sam, a developer who has never built anything with
Claude, through the course one skill at a time. In the drawings,
Claude is the octopus in the tank.
Sam finds one rule in code he has never seen
Delhivery wants to change who handles its most expensive cash-on-delivery parcels. The rule that decides this is somewhere in a ten-year-old codebase of about 1,800 files, and Sam asks Claude Code to find it.
If Claude reads the code folder by folder, everything it reads stays in its working memory for the session, which is called the context window. After 36 files that memory is almost full, and Claude still has not reached the file with the rule.
So Claude searches first, the way you would search a shared drive. The search points to 3 files, Claude reads only those, and most of its memory is still free.
Claude then changes the rule. Its first attempt is refused because the same line appears four times in the file, so it rewrites the whole file, and the change Sam reviews is one line long.
Sam teaches Claude Code how Razorpay's payments team works
Razorpay's engineers were typing the same team rules into every chat. Sam writes them once in a short file called CLAUDE.md, which Claude Code reads at the start of every session, and adds a check that stops Claude from writing card numbers into the logs.
Small jobs go straight to Claude. For a change that touches 48 files, Claude first writes a plan for Sam to approve, because the last time it skipped that step, 20 files had to be fixed again.
Sam turns the team's most used instructions into commands that anyone can run by typing a slash and a name, and shares them with all 40 engineers.
Sam connects Claude Code to the team's tools and has it check every change
Razorpay's engineers were copying tickets and records into Claude by hand. Sam connects Claude Code directly to the team's ticket tracker, code and payment records, and keeps the passwords out of the settings file that everyone shares.
PhysicsWallah has Claude review every change to the code that scores its mock tests. A bug that gave a skipped question minus one mark got past the session that wrote it, and a fresh review session caught it.
Sam builds a Swiggy help agent and sets limits it cannot skip
A Swiggy customer writes, “Where's my order? It's been 70 minutes.” Sam writes the program that sits between the customer and Claude.
Claude knows only what the program sends it. It cannot see Swiggy's orders or where the rider is.
So Claude asks the program to look up the order and the rider. The program does both and sends back the answers: the order cost ₹598, and the rider has not moved for 25 minutes.
Claude then asks for a refund, and the program issues it. Claude asks, the program acts and Claude reads the result, again and again until Claude has nothing more to ask, and this repeating exchange is called the agent loop.
Claude's reply goes to the customer: “Your rider hasn't moved for 25 minutes. I've refunded ₹598.” Chapter 7 builds this agent step by step.
Swiggy then opens the agent to customers who are not logged in. Claude was told to check who it is talking to first, but it skipped that check in 12 of every 100 chats, and one customer got a refund on someone else's order.
An instruction to Claude can be skipped, so Sam puts the check in Swiggy's own program, where it runs before every refund. A check of this kind is called a hook.
Small refunds go through on their own. When Claude asks for a ₹4,800 refund, the hook stops it and passes the case to a person in customer care.
Chapter 7: Agent loop opens on Wednesday 25 November
Chapter 8: Hooks opens on Wednesday 25 November
Sam gets clear answers from Claude and checks them
PhysicsWallah's automatic code reviews left so many unhelpful comments that engineers ignored two of every three. Sam rewrites the review instructions to say exactly what to report and what to skip, with worked examples.
Nykaa turns suppliers' PDF price lists into product pages. Claude fills in a fixed form for each product and Nykaa's program checks the numbers. When Claude misreads a price, one retry that points to the mistake fixes it.
Before its Pink Friday sale, Nykaa receives thousands of supplier PDFs a day. Work that nobody is waiting for goes through a slower batch service at half the price.
Chapter 9: Review prompts opens on Wednesday 25 November
Chapter 10: Structured output opens on Wednesday 2 December
Chapter 11: Batches opens on Wednesday 2 December
Sam builds a research team of Claude agents for Inshorts
An Inshorts editor asks whether Delhi's air this November is better than in earlier winters. The sources are too long for one Claude to read at once, so one Claude splits the question and gives each part to a helper Claude with its own short brief.
At first Claude kept sending a government bulletin to the wrong tool, because the descriptions of two tools read almost the same. After the descriptions are rewritten, 19 of 20 requests go to the right tool.
When the news archive did not answer, the search tool sent back an empty list, and the report then said there was no news. Now the tool says plainly that the archive did not answer.
Chapter 12: Subagents opens on Wednesday 2 December
Chapter 13: Tool descriptions opens on Wednesday 9 December
Chapter 14: Errors opens on Wednesday 9 December
Sam keeps long and large jobs accurate
One review of a 14-file change at Delhivery missed a time-zone bug. Reviewing each file on its own and then checking how the files fit together found it.
A Delhivery engineer works with Claude Code over several days. Naming each session lets them reopen the right one, branch it into two, or start fresh from a summary.
A Swiggy customer chats for over an hour and a half about three orders, and the agent starts mixing up amounts and times. Swiggy's program keeps the key facts separately and gives them to Claude with every new message.
The agent also hands chats to people. A customer who asks for a person is handed over straight away.
Inshorts wants its agents to read air-quality reports. Every number is saved with where it came from, so when the government's monitors and a private sensor network disagree, the story can report both.
Chapter 15: Decomposition opens on Wednesday 9 December
Chapter 16: Sessions opens on Wednesday 16 December
Chapter 17: Long conversations opens on Wednesday 16 December
Chapter 18: Sources and confidence opens on Wednesday 16 December
The five areas of the Claude Certified Architect: Foundations exam
Each chapter covers one of the five areas of the exam. Agentic Architecture & Orchestration is 27% of the exam and is covered in chapters 7, 8, 12, 15 and 16. Tool Design & MCP Integration is 18%, in chapters 1, 5, 13 and 14. Claude Code Configuration & Workflows is 20%, in chapters 2, 3, 4 and 6. Prompt Engineering & Structured Output is 20%, in chapters 9, 10 and 11. Context Management & Reliability is 15%, in chapters 17 and 18.
New chapters open each Wednesday until Wednesday 16 December, and the list
below gives each chapter's date.
An agent is your code running a loop around Claude.
Agentic Architecture & Orchestration
Wednesday 25 November
8
Hooks
Rules Claude cannot break: hooks, gates and handoffs
Agentic Architecture & Orchestration
Wednesday 25 November
9
Review prompts
Review prompts: explicit criteria and examples
Prompt Engineering & Structured Output
Wednesday 25 November
10
Structured output
Structured output: schemas, validation and retry
Prompt Engineering & Structured Output
Wednesday 2 December
11
Batches
Batches and multi-pass review
Prompt Engineering & Structured Output
Wednesday 2 December
12
Subagents
One coordinator, many subagents
Agentic Architecture & Orchestration
Wednesday 2 December
13
Tool descriptions
Tool descriptions decide which tool runs
Tool Design & MCP Integration
Wednesday 9 December
14
Errors
Errors Claude can act on
Tool Design & MCP Integration
Wednesday 9 December
15
Decomposition
Breaking big work into steps
Agentic Architecture & Orchestration
Wednesday 9 December
16
Sessions
Sessions: resume, fork or start fresh
Agentic Architecture & Orchestration
Wednesday 16 December
17
Long conversations
Long conversations and handing over to a person
Context Management & Reliability
Wednesday 16 December
18
Sources and confidence
Sources, confidence and human review
Context Management & Reliability
Wednesday 16 December
19
Exam scenarios
The six exam scenarios
Exam practice
Not yet published
Swiggy, Inshorts, Delhivery, Razorpay, PhysicsWallah and Nykaa appear in
this course only to explain how Claude Code and Claude work. None of
these companies is connected with these tutorials, and the code,
systems, numbers and events in the chapters were written for the
lessons. They do not describe how these companies work, and the
companies do not use this code.