[furyofantares]

With my current project (a game project), I full-vibed as hard as I could to test out the concept, as well as get some of the data files in place and write a tool for managing the data. This went great, and I have made technology choices for AI-coding and have gained enough skill with AI-coding that I can get prettttty far this way. But it does produce a ball-of-mud pattern and a lot of cruft that will cause it to hit a brick wall.

Then I copied the tool and data to a new directory and fully started over, with a more concrete description of the product I wanted in place and a better view of what components I would want, and began with a plan to implement one small component at a time, each with its own test screen, reviewing every change and not allowing any slop through (including any features that look fine from a code standpoint but are not needed for the product).

So far I'm quite happy with this.

[braaileb]

Where does the product description sit in your project so the ai can reference it? Is it like a summary form that describes what the project basically should do or be used for, asking for a friend

[furyofantares]

It's right in CLAUDE.md

For take #1 I said what tech to use and a high level description of the game and it's features. I guess I failed to mention this part, but when I threw take #1 away, I first used Claude + hand editing to update it to have a detailed description of each screen and feature in the game. So take #2 had a much more detailed description of exactly what was going to be built, but still, right in CLAUDE.md

I did also create a DEVELOPMENT-PLAN.md first with Claude and have been having it update it with what's been done before every commit. I don't know yet have a good idea of how impactful that part has been.