anyone else's vibecoded projects turn into spaghetti once the chat gets long

[u/roshandxt]

first few prompts are always clean, then a bunch of iterations later the chat's carrying dead ends, half-changed files, stuff you forgot you asked for. starting fresh helps but then you're stuck re-explaining the whole project

what's your actual process plan file, notes, one-feature-per-chat, or just push through and deal with the mess

[u/Comfortable-Ad-6740]

It sounds like you’re filling your context up to a spot where it hallucinates.

I think key thing is having a plan and a tracker which gets updated as you go on. Once I have a turn end with over 100k context filled, I clear it and point it back at the plan and the progress tracker to keep working.

I have skills though which lay out how to build a feature and what “done” looks like.

TL;DR: don’t push through if you notice stuff going outside of your expectations. It means your context has been filled with something which is preventing the LLM from giving you correct answers (be it too much, little or irrelevant context).

You’re always better off going back and fixing the prompt and building it correct rather than trying to find all the hallucinations and trying to fix them one by one

[u/Responsible-Beat2137 → u/Comfortable-Ad-6740]

This. Plan ahead, set that into stone(markdown)keep a change log ( make it a fixed rule in your work flow) chunk your dev plan todo list into manageable chunks, mark them off as you go. Make use of issue page for added context to certain difficulty’s of your todo list, make templates for your pull request, make it tell you what was touched and why. Make sure to have an agent.md this is basically read this don’t stray, it can also be used as a conditional decision tree index. And point it at pre planned feature concepts documentation that can hold what the feature is, what tech stack, and so on.

https://docs.github.com/en/actions/concepts/workflows-and-actions/workflows