Anthropic launched Claude Design on Friday. By end of Saturday I had a working cartridge that wires it into a structured development workflow. Not because I planned to – but because the architecture made it obvious. That’s the thing I wanted to test: whether FRAME’s engine/cartridge split actually holds[…]

Claude Code ships with two planning tools. /plan (or Shift+Tab to cycle into it) puts Claude in a read-only posture – it analyses your codebase, clarifies your goals, and produces a plan before touching a single file. Fast, built-in, no setup. For a contained task where you know what[…]

You’re 40 minutes into a Claude Code session. You’ve lost track of what you decided. Claude is re-reading files it already read. You’re not sure if you’re building the right thing anymore, and you’re not sure when you stopped being sure. This is not a Claude problem. It’s a[…]

If you’re working with Claude on a daily basis – whether that’s through the API, Claude Code, or just keeping up with what Anthropic is doing – you know how hard it is to stay on top of things. Model releases, API changes, Claude Code updates, community discoveries. It’s[…]

When you first discover Context7, the MCP path is right there in the docs. You know the drill: edit your JSON config, add the server entry, restart, verify the tools show up. It works. And if you’re already running a handful of MCP servers in Claude Code, one more[…]