I made Claude Code slower. On purpose. Here's why.

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 structure problem. That's why I built FRAME. What FRAME is FRAME is a set of Markdown files that give Claude Code a role to play and a gate to stop at. Nothing installs beyond copying a few files. No config, no runtime, no dependencies. You run /frame load sw-development and Claude Code knows it's a Requirements Engineer now, and that it doesn't move until you confirm what you're building. The core mechanic: a cartridge defines the phases, roles, and gates for a particular kind of work. The engine reads the cartridge and runs the session accordingly. You keep control at every gate — nothing advances without your y . That's it. The rest is Markdown. Two runs, same task I wanted to test this honestly, so I ran the sam