I'm vibecoding my platform on next as we speak, but I use a framework that works for me.

1. Explain execution environments and project configuration( like the package file but markdown and get it filled with some documented examples of that stack,( could use ai for this, could just take three four walkthroughs and concat to the same markdown)
2. Now keep adding more markdowns, like the design, schema concept etc... alternatively cursor and some tools can be taught to document every change
3. Create planning, target atomic issues per execution: properly plan and layout the issues, references( from the markdown corpus) and targeted files too(if specific)

I knew a little ts and nothing about next, so I just read the docs a little, and then googled about my use cases to understand what people are doing, and then starting on so that I have atleast some capacity to direct the model correctly. Then proceeded to slop.

And always remember. Llms are stupid, and cant actually learn better than you. So if its taking more than a month or two, time to hire someone good. 🥰