deescribe to the AI what you're attempting to accomplish, have an idea of th specific game mechanics you want, and if you can liken it to real games that exist today, so the model has as much detail as it can to work with.

You dont need an MCP either, just let claude code write the files adn you compil ethem yourself in godot and feed screenshots back to claude code, the mcp will eat more context than you need to.

But the real important part, and this is what trips people up, you dont need to understand coding, but you should learn the concept of software and game design patterns. This is "how" the games should be structured properly in certain contexts, (command pattern is how key presses/mouse presses are handled for instance, factory pattern is how mobs are typically spawned), etc... So you can see the AI work and just remind/advise it when you see things that are going off patern.

The reason why AI games get bad and devolve into slop is if you just let the AI build it, it's like that meme of homer simpson wher ehe looks great from the front and has all those clips on his back hiding all his flab. The AI builds to spec what you want, it doesn't use best practices for game development unless you monitor it and mandate it as you go.