@mvanhorn: TL;DR ELI5 of @trq212's new article: Claude isn't the bottleneck anymore. The stuff you forgot to tell it is. Your prom…

TL;DR ELI5 of @trq212's new article: Claude isn't the bottleneck anymore. The stuff you forgot to tell it is. Your prompt is a map. The codebase is the actual road. Every pothole you didn't mention, Claude fills with its best guess, and the more work you hand it, the more it has to guess. The skill of agentic coding is shrinking that gap. Your unknowns come in four flavors: what you said, what you know you haven't decided, what's so obvious you never wrote it down, and what you never considered at all Starting unfamiliar work? Do a blindspot pass: literally ask Claude to find your unknown unknowns and teach you to prompt better Know it when you see it? Prototype first. 4 wildly different HTML mockups is cheaper than one wired-up wrong guess Let Claude interview you, one question at a time, starting with answers that would change the architecture Can't describe what you want? Point at a reference. Source code beats screenshots, even in another language Ask for a plan that leads with what you're most likely to change: data models, interfaces, UX During the build: an implementation-notes.md that logs every deviation from the plan After: make Claude quiz you on the change. Only merge when you pass Every brainstorm, interview, prototype, and reference is a cheap way to find out what you didn't know before it gets expensive to fix.