Lay out the project folders
Where things go, before the model invents a layout per session.
I'm starting <one sentence> with <stack>, deploying to <host>. Propose a folder and file layout: - What goes where, with one line on each folder's job. - Which folder is the web root, and what must never be inside it. - Where configuration and secrets live. - Where tests go, if any. Follow the conventions people expect for this stack rather than inventing new ones. Keep it as flat as it can be for a project this size.
Save the answer in your project brief. Without an agreed layout, each new chat puts files somewhere slightly different, and after a month nobody knows where anything is.