Cairn: a thin SDLC for solo Claude Code work
A workflow layer for solo Claude Code that sits on top of the externalized context architecture. Four slash commands, one knowledge file, and a session protocol that keeps discipli...
A workflow layer for solo Claude Code that sits on top of the externalized context architecture. Four slash commands, one knowledge file, and a session protocol that keeps discipli...
Two months of running the agent-team starter prompt taught me which rules actually hold. The ones wired into tooling survived. The ones that only lived in prose were the first to e...
Six years ago I helped a CPG company dream up a smart meal planner. We never shipped it. This year, my wife and I built it — and we use it every week.
Running three AI agents sounds expensive. It's cheaper than running one — if you put the right model in each role.
Splitting a single AI agent into a team didn't just change the workflow — it changed how context flows through the whole system.
My AI coding setup worked — until I noticed I was spending more time checking output than building. The fix was giving the validation job to another agent.
I rebuilt my Claude Code starter prompt around .md files as external memory. Here's why and how.
Updated version of my Claude Code agent-teams starter prompt(/downloads/STARTPROMPT-AGENT-TEAMS-v2.md) after two months of running the previous cut on real p...
I rebuilt my Claude Code starter prompt(/downloads/STARTPROMPT.md) for agent teams. The original positions Claude as a single project lead that both coordina...
Claude Code has a `/memory` command that appends facts, preferences, and constraints to a `CLAUDE.md` file — either global (`~/.claude/CLAUDE.md`) or project-l...
I published my Claude Code starter prompt as a downloadable file: STARTPROMPT.md(/downloads/STARTPROMPT.md) It sets Claude up as technical lead for any proj...