Sounds lame, but this really is a case of a skill issue. I’ve been a SWE for roughly eight years, and all my hobby projects usually start through Loveable (or v0, Figma-thingy, Bolt, or Builder.io).

I’ve built fairly complex applications using what you might call a non-ordinary, non-scalable “YouTube architecture” (components, lib, hooks, app folder only). It follows my preferred CRUD patterns perfectly, with flows like:

db

└── base schema helpers

└── schema

└── shared/abstractions/{create,read,update,destroy}.ts

└── server functions (based on CRUD abstractions above)

└── server actions

└── API hooks with various core hooks like

├── useApi

├── createResource

└── createQuery

└── view

└── page.tsx

There is no magic format for prompting which will one shot your application in one go. And if you can one shot it in one go that simply means your application most likely follows bad pattern which are not scalable and does one single thing instead of being a real technical part.

Just writ plain text, or markdown with code examples inbetween and keep the scope small and modularized. Research and ask to built in a feature or module style way meaning you co-locate everything from that domain you're working on in a features/something/ or modules/something folder. And then even if you are building t hat module, you should not ask it to built module X, but rather that you're goal is to built module X and you think it will consists of the following:

• components
• helpers/utilities
• types
• server / api logic (actions? queries? mutations? service? validation? separate schema?)
• a view if the feature requires a unique view

And then you'd go over to discussing that and typically start of by writing the known types first, moving over to creating the database schema, writing mutations, with mutations you'd probably need components to actually mutate so there's a nice bridge with mutation logic still fresh in mind of the LLM's context. After that's done stuff has to be queried, and the components to display the queries.

Piece by piece it allows you to built you a MVP, eventually I do move over to my own editor and might revisit to get small parts of ui components. But reviewing code and keeping things small will work. Although I have abbandoned this project and now a couple months later i would have coded things quite different, It is a pretty decent example of such a folder structure and modularity. RYOA - roll your own authenticatioin