11 reads.
The clearest writing yet on why the model stopped being the bottleneck. Thariq's frame: the gap between what you asked for and what the work actually needs is where quality leaks out, and the real skill is surfacing those gaps before, during, and after you build. Worth reading twice.
A tight framing of the shift everyone's circling: you stop prompting the agent and start building the system that prompts it. Schedule, discover, build, verify, repeat. Worth it as the one-line mental model before you read anything longer on loops.
The best long read on why a top-tier model isn't the point. The system around it is. Loops, memory, verifier sub-agents, and state files are what make each run leave the next one smarter, and the piece lays out the whole stack with cost-routing advice for when to reach for the expensive model versus a cheap one. Long, but it's the map most people are missing.
An Anthropic engineer on two things the top model changes: self-correction loops and memory. The sharpest takeaway is that the model shouldn't grade its own work. An independent verifier explores harder and recovers from dead ends where self-critique stalls at good enough. Short, concrete, and from someone who actually ran the experiments.
The best explainer on the phrase everyone was repeating without defining. A loop is cron plus a decision-maker in the body: the model, not a hardcoded script, picks the next move each tick. The punchlines land, that the loop, not the model, is now the expensive part, and that the real asset is the skills a loop calls, not the loop itself. If you read one thing on loops, this.
A plain-English tour of the Claude features hiding in plain sight: Projects, memory, extended thinking, scheduled tasks, prompt caching, custom roles. Nothing exotic, but the value is in the framing. Each one takes minutes to set up and pays off daily. Good to forward to anyone still treating Claude as a fancier search box.
The clearest map of where interfaces are heading: agents drawing the UI in real time instead of describing it. Three patterns, controlled, declarative, open-ended, each with a different failure mode at scale, and most teams pick one by accident. If you build anything agent-facing, this is the decision tree to read before you're locked in.
The canonical piece on dynamic workflows, from the Anthropic engineer who built them. Claude writes its own custom harness on the fly to beat the failure modes of one long context window: laziness, self-preference, goal drift. The example prompts alone are worth the read, and it names the reusable patterns (fan-out, adversarial verify, tournament) you'll see everywhere else. Start here.
A design studio's field report on a real shift: the deliverable is no longer a PDF brand guide but a folder of structured files an agent can build from. The value moves upstream to the thinking, and the sharp bit is what they call magic_trick.md, the one human, left-of-center idea the system can't generate on its own. Best essay here on where human creativity stays scarce.
Karpathy on a workflow more people should steal: point an LLM at a pile of raw sources and let it compile and maintain a markdown wiki you rarely touch by hand. Once it's big enough, you query it like a research assistant, no fancy RAG required. The best part is that your own explorations file back in, so the knowledge base compounds. One of the most-shared AI ideas of the year for a reason.
The reference for anyone configuring Claude Code seriously. It walks the whole control center: CLAUDE.md, path-scoped rules, and hooks, with the key nuance that instructions are suggestions but hooks are deterministic. Keep CLAUDE.md under 200 lines or adherence drops. This is the one to bookmark.