Do not VibeCODE - do VibeSPECs instead

VibeCoding is writing what you want and magic happens - kind of. Great for party, useless for production.

So, in my company (where I was brought in as a consultant) many engineers have started to write detailed Specs before launching the vibecoding circus. Still the same AI vibecoding process, just a little bite more "professional" the old school way - they thought.

The crazy thing is, that they did the SPECs for the AI MANUALLY! How stupid! They have even followed a course and have bought a book!!!! about how to write Specs for vibecoding.

Then I showed them mine I have got GENERATED for a simple application and they were blown away.

So the point here and paradigm shift is the following:

Writing more detailed AI prompts does not help when apps are getting complex to start vibcoding from there!

What you have to do is - from the same abstract prompt - generating the context/configuration files VISION.md, SPEC.md, ... whatever your AI platform needs for context.

Never write these files yourself! Always generate them from your initial App description prompt. Then iterate over the such GENERATED Specs and when things are wrong or missing tell your AI to fix it - but never CHANGE those context files by yourself!

The funny thing is, that for non-engineers GENERATING the Specs rather than writing them manually, has always been the case. None of them would have dreamt of writing Specs by themselves. Its only engineers doing that. They really have to unlearn MANUAL Specs writing!

To give you an example how a modern SPEC.md looks -> check https://github.com/realB12/ApplAi_Generator/blob/main/VSC/client/AI/KIMI/CONFIG/SPEC.md

2 comments

Do not VibeCODE - do VibeSPECs instead