I think it's still vibe coding. In practice any AI-driven process where you tell the AI what you want and it writes the code is considered "vibe coding."

▲

therealpygon 3 days ago | parent [-]

No, it isn’t. There is a vast amount of difference between “vibe coding” and prompt driven development.

I’m giving the benefit of the doubt to the author here that it’s very unlikely they consider their example to be an actual representative scenario.

Vibe coding is to allow the AI to make the majority of the decisions. What the author describes is more like a highly complex autocomplete; you establish the fairly detailed outline of what is needed, often using tools/servers/etc tailored to use cases, and expect the AI to design an implementation that is in-line with the human-made decisions that preceded it, which is why I draw the comparison to autocomplete. Vibe coding is more like paying the kid next door to write your school essay…comparatively.

	▲	mleo 3 days ago \| parent [-]
		Agreed. There is a difference. I used vibe coding to build a UI prototype of workflow. I used mockup images as the basis of the layout and let the agent use Redis as the persistence layer. I know it will be throw away and don't care how it is working underneath as long as it can demonstrate the flow I want. I have also used prompt driven development to allow the agent to code something I expect to turn into a longer term product. I do more review of the code, ensure it is meeting all standards to development I would expect of myself or any other developer. There are certainly differing degrees of the two types of development.