Idea, filter, prompt, loop.

No code on this site was written by hand. Every artefact here started as a conversation.

The process begins verbally, talking through an idea with a language model at length, the way you'd think something through with a senior engineer. We discuss what the shape of it should be, where it might break, which parts matter and which are decoration. This stage is slow on purpose. Most of the thinking happens here, before anything is built. What comes out of that conversation gets saved as a markdown file, detailed enough to hand to someone else and have them build the right thing. That file goes to a coding harness with a prompt, and the harness writes.

Then the real work starts, reading what it produced, and nudging it. Not once, in a loop, back and forth, until the thing in front of you matches the thing you meant, or takes a path you did not expect. What matters most isn't the typing (it's all done verbally), on either side of the conversation. It's two other things: knowing which ideas are worth chasing before you spend an afternoon on them, and recognising when what's been built is wrong. Sometimes subtly, sometimes in ways that only show up under load.

Both of those get sharper if you've spent time working at every layer below this one. Neither requires it now. That's the trade this method makes, and it's made deliberately.

The barrier to entry has now dropped significantly.