I have been discovering this as I have gradually started to adopt AI more into our engineering workflows. Mine wasn't as structured and my reasoning had gaps that this article fills up. Difference between actually doing something and preaching it on YouTube lol :)
I was able to put it to practice and automate it to a point where claude automatically runs /close when needed and appends all the 4 files (as needed) , shows change log and seeks approval before finalizing.
Honestly Vibe Coding wasn’t our thing and loss of context was the biggest reason for that. You have provided a solution that every vibe coder needs whether they are aware of it or not.
I have been discovering this as I have gradually started to adopt AI more into our engineering workflows. Mine wasn't as structured and my reasoning had gaps that this article fills up. Difference between actually doing something and preaching it on YouTube lol :)
That’s awesome. This is behavior management in a way. It’s all about observing, which comes from doing. Trial and Error!
I was able to put it to practice and automate it to a point where claude automatically runs /close when needed and appends all the 4 files (as needed) , shows change log and seeks approval before finalizing.
That’s it! You got it. This compounds and is what will make you a 100x system architecture.
Share other patterns you discover in chat here. I’ll be writing a sharing many more.
Honestly Vibe Coding wasn’t our thing and loss of context was the biggest reason for that. You have provided a solution that every vibe coder needs whether they are aware of it or not.