It's just always been very behind the curve. I don't think you should use anyone's honestly. You should create your own shell base, and point to skills you find might add value, and add them. Then as you learn things about the shape of how things work, what you end up doing is rewriting them to follow your rules from what you learned.
What you'll find is, you'll have significantly better skills and systems.
Crap on it all you want, but it makes LLM work predictable.
If there's some clarity and structure with clear expectations, it seems to produce fairly reliable, consistent results, and the process of validating specs with Claude can yield all kinds of unexpected dead-ends or holes in the idea you had. I find this very helpful.
But I'm curious too, what are the skills you'd use instead? superpowers are just skills themselves.
Based on this definition, yep, I've been vibe coding since 2023. The products were less sophisticated, and I was copying and pasting one function at a time, but it worked. More important: it was something I couldn't do on my own.
The modern version is that bonafide engineers accept AI-generated code. It's a good thing I'm not a bonafide engineer.
Edit: a deeper look at the issues and there are many examples of it not behaving as intended. Seems superstitious at best.
It's just spottily enforced because it's just written to the context in markdown - it's basically one of the very first attempts from the very beginning of Claude code.
But superstitious would mean it's just in your head, essentially - but this has an effect. It does create questionairs, documents every decision and plan etc. Wherever you want that is up to you, I personally didn't... But it's also definitely very much causing an big difference in behavior from Claude Code