#claude-code
8 posts.
-
Your CLAUDE.md rules have an expiry date
I deleted three CLAUDE.md rules one at a time and reran the task. One was dead, one was cheap insurance, one shrank to a clause. Now there's a ledger for it.
-
My agents file bugs on each other
I dogfood my tools across my projects: agents file issues on the tool's repo, then message its session to pick them up. Context never crosses.
-
Agents by function, not by role
I asked what sub-agent system could build any kind of project, read the evidence, and ran four real trials instead of trusting a diagram. Two features shipped, one kit extracted: banneret.
-
Porting my homegrown GUI to a Claude Desktop mod
I missed coide's skills-and-agents panel after switching to Claude Desktop, so I rebuilt it in a day as a mod. How mods work, plus four gotchas.
-
Agents route around your hooks
A design-gate hook blocked nothing in eight agent runs. Nobody cheated. The agents wrote files through Bash, and the hook only watched Edit and Write.
-
I built "Context7 for your Rails app". Agents didn't need it.
Agents read your Rails code and find its conventions on their own. Eight A/B rounds showed a generated CLAUDE.md or AGENTS.md summary only got in the way.
-
Your subagents are zombie processes
Orphaned subagents keep running and billing after their parent moves on. The fix isn't a smarter model — it's a lifecycle contract Unix shipped in 1985.
-
Loop engineering, after the noise
Loop engineering means designing the system that prompts your agent instead of doing it by hand — with a concrete RSpec loop you can run on a Rails app today.