I Was Wrong About AI Coding Assistants. Here's What Changed My Mind (and What I Built About It).

3 months ago I was manually typing "act as a software architect" every time I needed architecture advice from Claude Code. 3 days ago I shipped an open-source routing engine that makes that unnecessary -- forever. This is the story of building PRISM Forge, what went wrong along the way, and 4 lessons about AI-first software engineering that I didn't expect to learn. The Problem I Couldn't Unsee AI coding assistants give you one voice. Smart, capable, generalist. But one voice. Need architecture advice? "Act as a software architect and..." Need QA? "Now act as a QA engineer and..." Need a code review? "Switch to code reviewer mode and..." I used BMAD-METHOD for 3 months -- a persona framework that requires manual invocation (*analyst, *pm, *architect). The concept was powerful. The friction was constant. I wanted the experts to just... show up. Once I saw the pattern, I couldn't unsee it. Every manual prompt-switch was a tiny failure of the tool to understand what I actually needed. The