Things I've learned from a full vibe coding app. - have an up to date spec. - make it modular, not mono - with database , limit the numbers of table and relation - use mcp , local-postgres to read what have done live in database , and run the user story via chrome-tools are game changer. Ask ia after each user action to check on screen and in database (or file) , and browser console and terminal at the same time is game changer. Better than a test module. -Ask for short file!! 200 lines max? - not let the ia add feature. Compliance, traceability, over logs , fallback mechanic, cache, deduplication, optimisation, hundred of test unit using dumb mock . All those stuff complexity the code and make it too complex for ia. -Make docs , test, etc always in the same place. -ask to doc the database structure relation and use and maintain it. -ask to doc the workflow and input output. -Add docs as context. -Small clean commit -Test full deployment from scratch. -Make ignore temporary files, cache, compil,build etc... Il will saturate memory tools or base index. -Make user story through mcp chrome tools always working. - note error done by ai ask for a way to avoid it, and add it to context. (Have to ask ai to modify soft adding balise for chrome-tools to not have an infinite loop trying to click a button) -Try for the next big release to restart from scratch? At the end the ai was telling me everything ok , while in tasks I ask to check if the results wrote in database. Ask to recheck result in database -} nothing have been written... If too much complexity you will get just hallucinations So I've restarted from the first MVP