Skip to content
jack in the loop

Writing

Things I learned the expensive way, written down.

claudeworkflowagentsfactorymemorymodspluginsqascheduledskills
  1. A brain made of plain markdown

    Claude doesn't remember yesterday. My setup does, in four layers of text files in git: global rules, per-project memory, decision logs, and shared research. What works, what doesn't yet, and a memory file you can copy.

    4 min · claude, memory, workflow

  2. Every bug becomes a check

    Claude ships pages that pass every test and still look wrong on my phone. So now there's a QA loop: render every page at real phone and desktop widths, in Chrome and Safari's engine, look at every screenshot, fix, repeat. And every new kind of bug gets added to the checklist for every site after it.

    3 min · claude, qa, skills

  3. Ten loops and a board

    For three months, scheduled Claude Code agents ran my product factory with no one at the keyboard: an idea generator, a scorer, a builder, a validator, a watchdog. 1,012 runs. How the loops fit together, what broke, and three patterns worth copying.

    3 min · claude, agents, scheduled, factory

  4. The orchestrator I deleted after a day

    I built a Claude Code mod that routed every question from every terminal through one inbox, plus a relay to my phone. It was worse than a read-only list that tells me which terminal needs me. What the mod does now, and the pieces you can reuse.

    3 min · claude, mods, plugins, workflow

  5. An orchestrator and a tracker for Claude Code

    Two skills that take work from ticket to production, and a couple of mods that tell me which session needs me. Prompts at the bottom to build your own.

    5 min · claude, agents, workflow