Very much not a skill issue; even with the best spec, guardrails and evals, frontier models will just do the hell they want.

> one-shot secure, performant code.

I call it reverse skill issue; it feels secure and performant because you can't verify properly, it feels right but it's actually broken in many nuanced ways. You can measure performance and produce a broken measurement as well. It's not as simple as you make it