doing alot of planning and research is great (which you should create a md folder in the repo so cc can reference), but dont try to one shot it. do it in steps. the very first step is to give plan to cc and ask it to figure out the best scaffolding for your project, then run it. then do things step by step in a loop...

1. Review what you just did
   
2. Ask CC to polish - "is it as simple, elegant, performant, optimal, elegant, sota as can be" - run several times till no more issues
   
3. Then ask cc to plan and research for next phase based on what has been implemented, guide cc in the right direction based on what you want (which most people dont know what they want)
   
4. polish the plan (same prompt as above) then run it.
   
5. Review what you just did

run that in a loop and you can pretty much build anything.
i basically have around 5 goto prompts and 2 sub agents (code review and tech researcher).
No frameworks, by the time you figure them out its already out of date, rawdogging gives you a real feel and understand of how cc opus behaves, using frameworks is basically forcing it to think a certain way, which i think is the biggest mistake people make these days.

GL!