i'm the same way, and my personal projects are being created in a similar way.

i'll have a specific technical architecture in mind -- API specs, a list of cloud services, a general idea about how code should be broken into modules. i'll write it all out and let the pieces get filled in by AI.

it's not really 'vibe coding' as the term was originally envisioned where you just describe a top-level goal (e.g., "make me a new version of minecraft. no mistakes please."). it's a different level of abstraction where the models are primarily doing implementation and not design.

for me this lets me do the fun parts of designing software BUT i don't have to slog through documentation and learn a bunch of DSLs to get it going.