

You tell it what the program does, it gives you a draft update each iteration you test it and tell the machine what went wrong, it’ll apologise too much and spit out the next iteration, repeat until successful
One project I vibe coded took four iterations before it compiled, I would have had more luck if I used a model optimised for code




More fun to write it yourself, but the give specification, get draft, give faults, get draft cycle is pretty fast after you have your initial spec ready (in your case the working code). Maybe a minute or two?