ai-llm
AI / LLM Integration
How to build features on top of large language models — feeding them your own data, letting them call your code, and checking that the answers are actually good.
Start track →Start from zero
Before the senior material: what LLM integration even is, and the handful of words the rest of the track assumes you already know.Prompt caching
Prompt caching: how a stable prefix cuts input cost 10x
Prompt caching reuses an exact token-for-token prefix at ~0.1x the input price. Any byte that shifts that prefix — a…
Tool calls
Tool calls: the round-trip loop, schema validation, and the guard against runaway agents
Tool calling turns a model into a function caller, but the model only emits a request — you execute it. Every call is a…
Rag architecture
RAG architecture: the pipeline that fails at retrieval, not generation
RAG is a retrieval problem wearing a generation costume. Chunk size, top-k, reranking, and context order each move…
Streaming
Streaming LLM responses: SSE, partial tokens, and the proxy that eats them
Streaming trades total generation time for time-to-first-token. SSE emits delta events you accumulate; tool-call args…
Cost budgets
LLM cost budgets: token asymmetry, routing, and the kill switch
Output tokens cost ~5x input, and the system prompt + history + RAG context get re-sent every turn — so a runaway loop…
Agents
The agent loop: ReAct, runaway steps, and context that grows every turn
An LLM agent is a while-loop that calls the model, runs a tool, appends the result, and calls the model again. The…
Evals
LLM evals: the regression test for non-deterministic features
You can''''t ship an LLM feature without evals: the same input gives different output, and a model or prompt change…
Putting it together
Composing a production LLM app: the bug lives in the seam
Caching, RAG, streaming, tools, agents, and evals each pass their own tests, then fail together. Trace one request end…
Build with this track
Guided projects that exercise what you learn here.
Engineering Practice
The habits that separate a hobby project from a professional team — testing well, shipping changes safely, and keeping a service healthy in production.