I am kinda documentation obsessed. Here are some of my documents for new project and you can see how they iterated to the next version.
I know I often see people vibe creating in gdevelop with and without the use of AI. But I cant stress how important a project bible is to start a project, and keep your bible up to date as the project advances.
Example I added Entity Component System (ECS) as a main philosophy to my bible. So now I know that all of my next prototypes of my game systems need to be structured and laid out that way.
Kinda boring but it is great practice. Then you can consult your documentations whenever needed and every project milestone you can review to see if any of the docs need updating or altering.
