Each time I tried it, with custom rules, git, and all the best practices I found, it went amazingly well initially, and garbage afterward.

Using the same technique, after a while, it generates a lot more shitty code than helpful.

> So, it’s shit and you’ll spend a long time fixing it.

It just takes more time overall to make it functional. Fixing, debugging and improving vibed code takes more mental resources and time than just writing it from scratch.

Also, there's the flow aspect. Each time you let it "vibe", you're losing the flow state that is important while creating and thinking about complex work.

The onboarding for other developers is also painless. I've recently experiment with AWS Amplify and even if is not quite there yet, is pretty close.

Lambda, cloudfunctions, https://supabase.com/, https://hasura.io/, AWS Amplify, https://aws.amazon.com/serverless/.

For frontend, I would go with either React or Vue, both with a huge community and already a lot of builtin solutions. I would 100% start with a design system, maybe material UI.

Nothing fancy, low maintenance and painless onboarding/development experience.