Marco012

I'm not sure if there is any standard for this, I also tried to search about it in the past. But what I ended up doing that has been working well is to keep everything documented. Every task and decisions are documented on .md files, referencing related tasks and decisions. The project becomes bloated quickly, but Claude can easily locate and relate decisions from a long time ago. Some times I even ask to do do something and mid-way Claude realizes that it goes against a previous written decision.

I honestly think that we just shifted from asset flop games to AI slop games. Nowadays we look at games and say "oh this is AI", but it doesn't mean you can't make a good game with AI. Obviously if we say "make the UI for my game", it will be, (from my experience), generic and not good at all. The same way we can just download an asset pack and slap it into the game. I totally agree that now we can spend time on game mechanics and quickly prototype different ideas much more easily, but it's not easy to make games. It's easy to make bad games, but still hard to make good ones.