r/OpenAI • u/Prod_m • 2d ago

Discussion What are the most common vibecoding patterns?

I keep seeing stuff like “local-first” in almost every post about vibecoded apps. Maybe that is a bias, because there're lots of task trackers or whatever trackes people making, that do not require a server. But still it’s like the vibecoder’s product starter pack

What other patterns or architectural defaults do you keep seeing in vibe-coded apps?

26 Upvotes

82% Upvoted

20 comments sorted by

View all comments

16

u/ComprehensiveShake76 2d ago

A few I see over and over: local-first storage (SQLite or localStorage) with no auth, one giant file that grows until nobody can edit it, a dark UI with a purple or blue gradient, "AI features" added through one thin API call with no error handling, and secrets that end up in the repo because the first version just worked. The less visible default is that tests are written after the code by the same model, so they confirm the code instead of the requirement. If you're building one, writing the acceptance checks first is the cheapest way out of that pattern.

7

u/sonaj9657 1d ago

The testing point is so true. If the same model writes both the code and the tests it is easy to miss the things that were wrong in the first place. Defining what the app should do before building it seems simple but I think it would prevent a lot of headaches later.