Blog
Notes on building with Claude Code.
Deep dives on MCP servers, hooks, agents, and the operational side of shipping AI-first workflows. No fluff, no "top 10 AI agents of 2026" lists.
Skills, subagents, slash commands — a decision tree for Claude Code
Three customisation mechanisms in Claude Code that people conflate constantly. When to reach for each, what they cost, and the one anti-pattern that ruins all three.
Read post →
Production-grade MCP servers: the three things every open-source one gets subtly wrong
A field guide to building MCP servers you'd actually put in a team's shared config. Error handling, testing strategy, deployment patterns — and the failure modes I see in almost every MCP server on GitHub right now.
Read post →
I built an MCP server to triage my sales inbox. It can read and draft — but it literally cannot send.
A case study in deliberate constraint. Building a Claude Code MCP server for Gmail that reads one label, drafts replies to the Drafts folder, and has no capability to send or delete — three independent safety layers, 55 tests, and a design I'd trust on a shared account.
Read post →
Claude Code hooks that don't break your workflow
Four rules for writing Claude Code hooks that catch real problems without annoying you into disabling them. With two working hook scripts (secret-blocking + bash logging) you can drop in today.
Read post →
The Claude Code deny-list most teams skip (and how it eliminates a class of disasters)
Why a five-line deny list in your .claude/settings.json is the cheapest foot-gun protection in Claude Code, what to put in it, and how it interacts with hooks.
Read post →
I built an MCP server to plan this blog. Here's the code, the ranking logic, and the first 10 ideas it surfaced.
A walkthrough of building a Model Context Protocol server that mines Hacker News and Reddit for content opportunities, ranks them with a simple 5-signal heuristic, and surfaces ten unanswered questions developers are asking about Claude Code and MCP.
Read post →