I found that project setup is very important. I use extensive documentation in the process.
Cursor rules (always apply)
Behavior rules: how the model should behave. I had grok 3 with deep search look into community discussions for the model i use to write it. this helps the model avoid its common pitfalls
Informed responses: just explicitly tells the models that it has a bunch of tools and it better use them
project rules, PRD-inspired for the model to understand overall project structure
The plan.md is extremely helpful and i always keep it up-to-date by simply asking the model once in a while to mark its progress an update action items if the list has changed in the process.
And then summaries and new chat as described.
With gemini 2.5 pro, this has been incredibly productive over the past few days. I made 2 weeks worth of progress in this time.
Let’s pair zero-shot or one-shot prompting with strict token limits to minimize unnecessary deviations. For instance, if you’re working with Claude 3.7 Sonnet, cap the output tokens to ensure precision without overcomplicating things and use lightweight models for initial drafts or exploratory work to save resources and reduce hallucination risks.