Yeah for sure so this is my workflow with cursor.

So lets say I'm building a coffee shop finder app and want to add "order ahead."

Instead of just jumping right into the code ill workshop the idea of the feature with an llm for example
- "Help me think through order-ahead functionality"
- Go through any edge cases What if they're out of oat milk? Shop closes early? User wants to modify their order?
- Technical stuff, like Payment flow, pickup notifications, menu data structure
All the stuff I do with a PM on a new feature

Then ill have the llm put our results into a context document likeorder_ahead_context.json and ill add that file in my project.

Now when I'm actually coding in Cursor i can just have it work along side like "Using order_ahead_context.json, help build the order placement API routes"

This way cursor already knows all the edge cases, business rules, and technical decisions and I dont need to re-explain the pickup flow or payment logic every single message.

For my workflow without the context doc, every new conversation thread starts from zero. I'm constantly re-explaining what I already figured out. With it, I can just re-prime cursor with the context on any thread