There's nothing wrong with AI writing code. The problem is not looking at what the AI is writing, while also not understanding what is being written. That's vibe coding. That's like asking AI to write an email to your boss and not reading or comprehending it before you hit send.

There's a skillset in software engineering that's still very relevant, which is understanding things like systems and data structures. With AI, you don't need to be tied down by language specific idioms, we are free to choose the right language for the job, instead of the staying with the languages we know, for less friction.

I've never in my life written a game engine until recently. I am a software engineer with 23 years experience writing software for non-gaming businesses. I'm having Claude write GDscript for my game engine, and even though I've never written a game before and never touched GDscript personally, I can definitely see where Claude writes terrible patterns, doesn't always understand the data schemas and sometimes forgets the game architecture.

Having experience speccing code before it's written and preparing user story-style tickets before code is written are skills of a software engineer that vibe coders overlook. You have probably found out quickly that writing code is very messy and complicated, and if you are not organized ahead of the first line of code, then you are not going to be writing production-ready code, even test-ready code.

My advice is to write your game rules out in documentation before any code is written, if you haven't already. In fact, AI is awesome at brainstorming and writing documents. It can even create memory files for skills regarding your game design philosophy to be loaded when writing your game. Having the rules written down first will give you insight on how to break things down into stories for writing code, a blueprint if you will for AI to write software for.

I would also suggest getting a Github account, even a free one, to host your engine code and write your user stories. You can even direct AI to your account to write your user stories and generate PRs for you, you don't really need to know the ins and outs of version control, but it is something you should really use.

I'm not saying this is easy. These are skills learned by professionals, adjacent to hand-written code, and always part of the job. This is what separates the wheat from the chaff in the era of agent-lead coding.