If you want to vibe code a maintainable project, you need to spend the first month chatting to outline a good codebase structure before you ever write your first line. Unless you know what you want to do and basic knowledge of your general purpose language, AI will only help you make slopware that never sees production.

On the other hand, it's an invaluable tool for weighing all the possible options in how to do what you want. For instance, it's great if you want a comparison of all the ways you can make configurations for your project. Or a comparison of database options. But if you just go in and let it decide things like this from the get go, you're going to have a very hard time maintaining it when you get to a thousand lines and realize you would rather use a SQL instead of a document store or a yaml instead of an env.

You have to know what to tell the AI to build. If you don't mention tailwind, your gunna get a shitload of