If your specialization is in coding, then it is unlikely that you should (regardless of whether you actually do it) be vibe coding for production work. There are much better patterns for professional use, like using it as a sounding board, prototyper, or even as a tester (if you are actually going to read all the slop it produces.)

If you're not a pro coder, then, as long as you don't be vibe coding for production work that you cannot build yourself, you're fine. I use it a lot in R&D when I otherwise can't be bothered to spend the time coding something up, because I want to emerge in the subject and not spend hours building tooling to enhance the research. For this, it is awesome: tool building.

But you have to be able to make decisions on what the LLM should produce for you, and this is the hard part. LLMs aren't really trained for this role so it's not like you can ask it how it can help. Look at a coding LLM as a junior data scientist or staff coder that you have to carefully instruct, and only when needed, otherwise they will waste your time. If you're rich, you can hire a non-LLM (i.e. human) to instruct the LLM for you: this is a real skill and it is not lazy work.

Honestly, the only way to develop the skills to instruct LLMs coding tools for you is by spending the time, and by making mistakes. Should everyone do it? No. Should you just ask your LLM what it could do to help? No. But you can definitely vibe code a need up, for something that you're doing manually right now, or that you're postponing because it takes so much manual labor. And if it sucks then you learn.