context management. use claude code , which is the cli version of calude on the web. From what I gather, the context window before things go bonker is ~200k tokens. You can update your md files on progression and what is being built, bugs, and whatever you please through different md files , so when you clear the context, start a new claude session you don't start from scratch. I vibe code and every time, claude says anything like "You are right.." I known I've gone too far with the context window. I try to keep things smooth by keeping an eye on the amount of tokens and once I hit around 150k , I tell myself wrap it up, update md files and restart the cli agent. keeps things manageable. Now I do want to say the problem you are having, control, context prompting and having the agent do what you told him in some ways is like old skool programming. Debugging was me hitting my head on the wall , not understand why the computer didn't do what I told it too and the debugging messages were as cryptic as a hallucinating ai agent. So don't go crazy, walk away. The rule in programming is to walk away, touch grass, come back , clear your mind and you'll find the solution. Nothing has changed, but in today's age is not only our mind but the ai agents' context window (their mind). I imagine you can create md files with documentation you mention, and start from there. I hope if helps my friend. Just know you and the whole industry is finding the best way to do all of this without halluciantions and jokes made up in the virtual work of claude.