The trick when vibe coding, if you got a feature working, commit it.
Don't be greedy and try to stack more features, it will be difficult to unwind and go back to the feature that was working.
probably smarter devs will know how to go back, but I vibe coder like me will be stuck.
it's like not hitting save and needing to go back to an old checkpoint.
Real af
Best process I have found so far is
1 write your issue in GH
2 write a process doc locally for your AI to follow so that on a new session its bootstrap is:
1 reads process doc
2 reads GH issue and all comments
3 checkout new branch
4 code
5 add commit and push new branch with comment
Then you engage to review at that time
If it needs tweaks or whatever, make them
If its context is starting to blow out, start a new session and have it read comments and diffs in its bootstrap
If it has failed too badly:
1 have it write a post mortem and add as comment to the GH issue
2 delete branch and session
3 start again, and its bootstrap will be enhanced by the post mortem of the failed session
Just create a branch at the beginning and make every output a commit
Learn GIT. And if you are in VSCode, use GIT graph to get a visualization of your GIT.
