I use an iterative workflow to turn vibe-coded projects into real engineering: inspect what happens, investigate the code and logs, document problems and fixes, and repeat.
I start by running the project and observing pop-ups, layout misalignments, unexpected behaviours, and errors.
I read the relevant code snippets to investigate the project.
For backend work, I observe and analyse as many logs as possible.
I acknowledge that I do not know everything, and prompt AI as much as needed while researching different ways to troubleshoot problems.
I write well-engineered prompts rather than vague requests such as “I'm getting errors, just fix everything.”
I create a solution.md file to document the problems, write a well-structured prompt, and let AI implement the fixes.
I document the problems I encountered, the solutions I discovered, and the fixes I actually applied.
I repeat the process to turn vibe coding into real engineering.