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 many people have start to write detailed Specs. Still the same process, just more "professional" - 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 and paradigm is the following:

Writing more detailed prompts does not help when apps are getting complex - WHEN you start vibcoding from there!

What you have to do is - from the same abstract prompt - generate the VISION.md, SPEC.md, ... your platform needs for context. Never write those files yourself! Always generate them from your initial App description. Then iterate over the GENERATED Specs and when things are wrong or missing tell you AI to fix it - but never CHANGE those context files by yourself!

The funny thing is, that for non-engineers that 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

1 comment

Do not VibeCODE - do VibeSPECs instead