Build
Walkthroughs where the thing actually gets made. You see the finished result first, then we go back and take apart the part that made it work.
Your first CLAUDE.md: the four boundaries that matter
Everyone's instinct is to add more rules. Removing them works better. Four boundaries, and why each one earns its line.
The DESIGN.md that kills the AI look
Models default to the same gradient-and-rounded-card aesthetic because nobody gives them constraints. Here's the file that does.
A model router that stops you burning your usage limit
Most of what you send to a frontier model doesn't need one. The routing setup, plus the rule for deciding what goes where.
Wiring your first MCP server (and locking it down)
How MCP actually passes data around, why a careless setup can expose your API keys, and the 60-second audit for the one you already have.
Three files, one session, one working SaaS
The exact order I hand Claude Code context in, and what changes when you get that order wrong. Full build, nothing cut.
Auditing a pricing page against Stripe's copy rules
Most people point a model at a blank page. Point it at the page you already have instead. It finds the line costing you signups.
Running a 3B model locally that beats ones ten times bigger
Offline, on your own machine, no API bill. What it's genuinely good at, and the tasks where it falls apart.
Automating a whole content pipeline with n8n
Notion to scheduler to stats, wired end to end. The dev advantage nobody in this space is using.