A frame to help you reason through the assignment — concepts, diagrams, and the API map. It deliberately does not contain the answers or filled-in activity code. Instead it gives you the questions to ask yourself and the method to get there. The work — and the learning — is in running the cells, reading the decision tables / cache timings / the A2A trace, and writing your own conclusions.
Session shape: THREE independent parts — two notebooks + a runnable
a2a/mini-project. The notebooks are fully worked (no blanks to fill): your job is to **run them, keep the outputs
A frame to help you reason through the assignment — concepts, diagrams, and the API map. It deliberately does not contain the answers or filled-in activity code. Instead it gives you the questions to ask yourself and the method to get there. The work — and the learning — is in building the app with Claude Code, reading the message stream, and writing your own conclusions.
Source:
11_Claude_Code/README.md(markdown-only session — no notebook; you write your Q1–Q4 answers directly in the README). Guides:01_Installing…,
A companion to the four session guides (README.md, 01_Installing_Claude_Code.md,
02_Using_Claude_Code.md, 03_Claude_Agent_SDK.md). It's a validation log: every
command and API call in those guides was checked against the official Claude Code /
Claude Agent SDK docs (and against the real installed SDK), so you don't lose time on a
stale flag or a wrong field name. Use it as a "known-good" reference while you install,
drive Claude Code, and wire up the agent. All the doc links you'll want are collected in
References.
A step-by-step companion to
README.mdandENDPOINT_SETUP.md. Walk this alongside the assignment, not instead of it. Each step tells you what you're doing, why it matters, what will bite you, and the lesson to carry forward. The README asks you to answer the questions and build the app — this journey helps you understand what you built.
A frame to help you reason through the assignment — concepts, diagrams, and the API map. It deliberately does not contain the answers or filled-in activity code. Instead it gives you the questions to ask yourself and the method to get there. The work — and the learning — is in deploying the endpoint, running the cells, reading the output/traces, and writing your own conclusions.
Repo:
10_LLM_Servers/—endpoint_slammer.ipynb(endpoint test) + anapp/
A frame to help you reason through the assignment — concepts, diagrams, and the API map. It deliberately does not contain the answers or filled-in activity code. Instead it gives you the questions to ask yourself and the method to get there. The work — and the learning — is in packaging the agent, inspecting a Studio/LangSmith trace, shipping it, and writing your own conclusions.
Source repo:
09_Agent_Servers/(a packaged LangGraph agent + a Next.js
What this is. A client-first, problem-driven path through the Cat Shop server. Instead of building the finished server bottom-up, you start with the smallest thing that works — one tool and a local client you write yourself — and add one capability per layer, each because you hit a wall the previous layer couldn't pass. Every layer ends with a command you run to validate it, and a diagram that grows as the system does.
Two editions, pick your style. This is the companion to
08_MCP_LEARNING_JOURNEY.md(the Build-From-Scratch edition, which reconstructs every server file top-to-bottom). They teach the
What this is. A guided, type-it-yourself rebuild of the Cat Shop MCP server. You will reconstruct the server one layer at a time, run a checkpoint after each layer, and answer a short understand-it question before moving on. By the end you'll be able to explain every file in
app/— and you'll be ready to add your own tool (the graded Activity).How to use it. The finished server already ships in
app/. So you have two ways to travel:
- Build mode (recommended): create a new package folder
catshop/next toapp/and type
What this is. A guided, type-it-yourself rebuild of the Cat Shop MCP server. You will reconstruct the server one layer at a time, run a checkpoint after each layer, and answer a short understand-it question before moving on. By the end you'll be able to explain every file in
app/— and you'll be ready to add your own tool (the graded Activity).How to use it. The finished server already ships in
app/. So you have two ways to travel:
- Build mode (recommended): create a new package folder
catshop/next toapp/and type
A frame to help you reason through the assignment — the concepts, diagrams, and API map. It deliberately does not contain the answers or a filled-in tool. Instead it gives you the questions to ask yourself and the method to get there. The work — and the learning — is in reading the server code, running it, connecting a client, and writing your own conclusions.
Source repo:
08_MCP/— entry pointserver.py, server packageapp/(server.py,tools.py,oauth.py,routes.py,db.py). There is no notebook this session — Q1/Q2 are answered inREADME.md, and your code deliverable is a new@mcp.tool()in