The definition may have changed but I feel like originally it was only vibe coding when the “dev” did not know what they are doing. When some one with little to no programming background is able to build and app on “vibes” alone.

I don't think the two cross, really. A vibe coder asks for a bunch of features and then starts refining the output, fixing bugs and adding features. A developer knows the specific architecture and from years of writing tasks knows how to break work into manageable chunks and uses AI to implement something they have already defined and know where it fits in. The skill to write a good story isn't far off from writing a good prompt.

I use AI all the time, and every time I hear someone describing vibe coding it makes my skin crawl.

I'd say the use cases of: mundane but time consuming, pointed inquiries or interactive rubber ducking, are all getting AI help. Offloading a design where you don't have a clear understanding of how it should be done is vibing.