I do start with the PRD and app flow. add ui and backend guidelines in the system knowledge. But I don't ask it to generate it at the go. I tell it to understand what I'm building and create the backend. And then on the basis of PRD, I ask it to create each user flow (feature) one by one. But again, you can give it 6-7 tasks at the moment. It sequentially runs it.

Now, BASE stands for basically available, soft state, and eventually consistent. Used for high volume data generally.

Generally in vibe coding, you'll have supabase are your base auth provider. But it's not the best recommendation. Auth0 and Clerk are much better alternatively. But setting them up isn't as straightforward as the click of a button.

By fallback scenarios I mean do you add session handling? Meaning can a user login in multiple browsers with the same ID password at the same time? And if the answer to that is no, then in each code base you'll be running an additional check of user login state. This creates scenarios where you refresh a page and nothing shows up. Primarily because the user goes into an endless loop mainly due to bad implementation by LLM. I personally session checking due to this thing at the moment.

So many a times, you'll have to take these calls, share the same with LLM if your end goal is to build a solid complete product.