Notes from the workbench.
Thinking out loud about PHP, AI tooling, ABA software, indie hacking, and whatever else I'm shipping this month.
I Went on Vacation and My Agents Paid Down My Tech Debt
I took a week off and let Superconductor loose on a 500k-line Laravel codebase. It opened roughly two dozen PRs a day: N+1 fixes, unbounded job processing, missing HTTP timeouts, tenant-scoping bugs. I merged 98% of them. This is the setup that made that safe.
Turning a Creator's X Tips Into Agent Rules Claude Actually Reads
I follow Povilas Korop for Laravel tips, but they scroll by on X and vanish. So I scraped ~696 of them, OCR'd the code-in-image samples with Claude, and distilled the durable ones into versioned agent-rules repos my coding agents load automatically. Here's the whole pipeline.
My Global CLAUDE.md: The Rules I've Built Up Over Time
Every time an AI agent burned me, I wrote a rule. Here's my entire ~/.claude/CLAUDE.md — the personal rules that travel with me across every project — and the scar behind each one.
A Linear workspace per project in Claude Code (no more reconnecting)
If you work across two projects with two different Linear workspaces, Claude Code's Linear MCP makes you disconnect and reconnect every time you switch. Here's how to bind each repo to its own Linear account so it just works.
Stop stuffing every AI rule into one root file: apply-agent-rules
Most projects pile every AI agent rule into a single root CLAUDE.md and the file balloons past a thousand lines. Subdirectory rule files are a much better idea — and apply-agent-rules makes them practical.