topic · ai workflows

The tools change every quarter. The systems you build around them are what compound. This is where CTRLSZE writes about context engineering, CLAUDE.md patterns, MCP servers, and the operational scaffolding that turns one-shot prompting into a reliable workflow.

• How I used to work with Claude, and how I work with Claude now

  Shipping UI with Claude Chat, Design, and Code falls apart at the handoffs. Here's the seven-fix loop that replaced my old vending-machine workflow.

  23.05.26

• The many shapes of Claude: which one to use when

  claude.ai, claude code, the ide extension, desktop + mcp, computer use, the api — same model, different wrappers. when to use each, and where each one breaks.

  21.05.26

• The Website Performance Testing Tools I Actually Use

  No single tool tells you the whole truth about web performance. Here's the working set — pagespeed, webpagetest, crux, RUM — and what each is actually good for.

  15.05.26

• Context engineering is the only AI skill that compounds

  Every model gets replaced. Every IDE gets replaced. The system you build around them is the only thing that survives the next release. Here's what mine looks like.

  12.05.26