I haven't seen "just absorb a giant ball of context and do the right thing the first time"

Exactly.

No more than sitting down and writing code before a product concept or spec or architecture comes out right the first time, or fifth.

Absorb the concept, make a shape of outcome, then a spec, then hold its hand to architect a series of iterations, either component by component or thin vertical slice or whatever combination lets you iterate in working increments...

Your brain, machine leverage. After all, it types faster than you. But it should type what you want.

You know what it should type, right? If you don't, you're gonna have a bad time anyway.