Cursor Prompting HandBook:

1. "Fix Errors" Prompt AI models like Sonnet 3.5 can overlook important details sometimes and that triggers a loop of errors. Use this prompt below to fix that issue. This will help AI to analyze the caore cause of the error and then create a step by step plan to fix error.

2. "New feature" Prompt Once you execute one component successfully, you need to refer AI to docs again to make it understand the scope of work for next componemnt. Use these instructions to make AI write an implementation plan before execution. Tag the relevant doc, and once AI read through the file, it might ask you questions. Answer the questions and ask it toexecute. This one step will kill half of hallucimations for every component.

3. Response structure: This structure provide update to AI that the task I was working on is DONE and now I need to move to NEXT task. 1. Provide update: "Header menu is now aligned in center perfectly." 2. Provide next task: "Now we need a sign in and sign up buttons." 3. Tag right document: "Check @ (document name) and explain how you will implement this"

4. progress .md file Use this prompt to keep track of all the work. This will provide progress context to AI and solve the duplication errors. "At the end of every completed step record your work log in @Progress .md file. What features we implemented? What errors we encountered? How did we fixed all those errors. Answer these 3 questions in a step by step manner and DO NOT miss any information."

5. project-status .md file AI should pick up the work from where we left. This file will help AI keep worklog and understand whats already done and what's left. "At the end of the session record your work log in @ project-status .md file. First check @ progress .md file to understand all the features we have implemented in this session. Then write a detailed session report which should provide detailed context for next work session"

6. Cursor Agent Hack Cursor agent can over do things and mess up the codebase. "Read instructions in @ (document name) to understand the scope of work for this feature. Use chain of thought reasoning to create a step by step implementation plan. Ensure you explain how every section of this feature works providing macro-level details. Break these items into detailed numbered steps." This will provide you plan that AI is about to implement. You can verify is everything is aligned with the request and approve. This will solve all unnecessary edits by Cursor Agent.

7. Attach Documents. Create a "Documentation" or Instructions" folder. The attach all core documents under that folder. - Project Requirements Doc (PRD) - App Flow Doc - Frontent Guidelines Doc - Backend Structure Doc - Tech Stack Doc - File Structure Doc you can use 01 model but with right prompting (it can overkill with unwanted sections and fluff information)

The best solution is to get these documents done with @CodeGuide I automated this process for you. It'll help you get all required docs in 20-30 minutes. Using a mix of Sonnet 3.5, o1-preview and GPT4o for docs creation. Usually it takes 7-8 hours of work to get all documents ready with ChatGPT (reading, refining, iterating each doc)

That's all for today. Bookmark the post future use. Build amazing things. Sign up for http://codeguide.dev Limited time 30% off on Yearly plan. CodeGuide 1.2 is coming in 3 days.