feedback: your psuedo code example is just product requirements and not actual psuedo code. and I think if you wrote psuedo code it would just work as is without a skill

Btw, I got inspired by this: https://www.williamjbowman.com/blog/2026/03/05/against-vibes...

Really useful read!

Great point on the flow state with pseudo code. The gap I keep running into is what comes after – once the translated code ships to production, knowing quickly whether it actually behaves as intended is still mostly manual. Curious if others have thoughts on that part of the loop.

Translating pseudo-code to real code is almost table stakes for any decent LLM at this point. But getting architectural feedback in the same abstraction layer you think in, that's a different thing entirely. I've noticed something similar when working with Claude Code. The quality of the back-and-forth improves significantly when you stay at the intention level rather than jumping straight to implementation. Once you're in the weeds of actual syntax, the conversation tends to collapse into micro-corrections. Staying pseudo keeps the design space open longer. One thing I'd be curious about: how does it handle the translation when your pseudo-code has ambiguous control flow? That's usually where I hit the wall. The semantic intent is clear to me but there are three or four valid ways to implement it and the model just picks one without flagging the decision.

> The LLM will suggest changes (design, architecture, functionality, ...) to your code, but will roughly use your pseudo code style.

So it will change your architecture, but keep your line-by-line logic? Is this like a self-driving car that takes you to the wrong destination, but accurately follows traffic laws on the way?

Give me the opposite - something that builds exactly what I designed, but has the freedom to get there in better ways than I suggest.