CLAUDE CODE
★ LatestBuildNotBurnClaude CodeApr 27, 2026· 4 min readAI
Engineer Your Claude Skills, Don't Just Prompt ThemMost developers treat Claude like a chatbot. They type the same instructions every session, hoping for consistency. I build behavioral skill files instead — reusable modules that compound across projects and turn vague intentions into reliable outputs.
Read the full note →BuildNotBurnDoctrineApr 24, 2026
Gravel vs BRICKs: The Framework That Changed How I Measure a Build Session
I used to end build sessions exhausted but unsure what I'd actually shipped. Then I started categorizing every task as either GRAVEL (busy work) or a BRICK (deployable output). The difference isn't what you'd expect.
4 min
→
BuildNotBurnDoctrineApr 22, 2026
Why Your CLAUDE.md Is Wrong (And How to Fix It in 20 Minutes)
Most CLAUDE.md files are glorified wishlists that Claude ignores. After 6 months of daily Claude API work across four products, I rebuilt mine from scratch. Here's what actually works.
4 min
→
BuildNotBurnBrandApr 20, 2026AI
How I Run 4 Distinct Brand Systems Without Losing My Mind (Or Mixing Up the Voice)
Managing four separate SaaS brands means four color palettes, four voices, four sets of design tokens. Here's the system I built to keep them straight without constantly context-switching or shipping the wrong brand's blue.
4 min
→
BuildNotBurnClaude CodeApr 20, 2026
One File That Changes How Claude Knows You
I run four SaaS products solo. For months I explained the same architecture to Claude at the start of every session. Then I wrote one file. Here's what changed — and what it took to get it right.
7 min
→