I tried several different models and modes, but Claude 3.7 Sonnet on Agent mode quickly became my default for everything. It’s much better than the other models.

3.7 Sonnet on Agent mode can go way overboard sometimes, fixing things that weren’t broken, and causing stuff to break. Particularly when it comes to CSS changes. Sometimes it’ll accidentally delete (or unnecessarily add) hundreds or thousands of lines of code. When this happens, I just revert the changes (restore to the previous checkpoint) and re-send my prompt, along with a note like “only make this change; do not do anything I didn’t ask you to do!” That usually works to keep it focused on the right thing.

You can edit the code yourself, and Cursor will keep your changes (as long as you save it! CTRL + S to save on Windows). Sometimes this is easier than asking Cursor to make a change, especially if it’s something minor like changing the padding or color of an element.

If there’s something you don’t know how to do, just ask Cursor to walk you through it step-by-step. For example, I didn’t know how to deploy the site (forgive me, I’m used to WordPress, not hand-coded sites lol). So, I asked Cursor to walk me through deploying the site on Hostinger (my web host). I followed all the instructions, and it worked! Now I know how to deploy simple hand-coded sites yay.

Sometimes, a feature isn’t worth adding. I wasted 3 days trying to add a popup that ONLY showed up for non-logged in users encouraging them to create an account to save their scores and appear on the leaderboard. However, this popup would briefly display for logged in users as well, and after hundreds of prompts explaining the problem and asking Cursor to fix it, the issue persisted. I even gave all the code to ChatGPT and asked it where the issue was, then fed that response into Cursor, but that still didn’t work (and I tried this dozens of times, and each time ChatGPT found a different issue that actually wasn’t the real issue). In this case, 3.7 Sonnet finally identified that the issue was due to the site being static. I would need to set up an authentication check at the server level in order for this feature to work seamlessly, but that was beyond my technical expertise. It’s probably not that hard, but I decided that having the popup wasn’t worth the headache, so I removed it entirely.

Connect Cursor to Github so you don’t lose all your work. Relying on the “Restore checkpoint” button in Cursor isn’t always enough. I lost hours of work at one point because for whatever reason, Cursor kept some buggy code even after restoring to a point before that code was changed. Connecting to Github for version control would’ve saved me quite the headache. Ian Nuttall has a good video showing you how to connect to Github (I feel like this is a good time to mention that Ian Nuttall and I are NOT the same person. We get mixed up pretty often lol. He’s on a completely different level than me, you should seriously go follow him).

Download it from the Cursor website

Start a new project by clicking “Open project”, and then create a new folder with your project name. Select that new folder and open it in Cursor. Alternatively, you can clone a Github repository or connect via SSH.

Explain what you want to build in the chat box. Better yet, first explain it to ChatGPT and get a full outline/PRD for your project, then paste that into Cursor’s chat.

Learn more and stay up to date about Cursor on Playbooks and by following Ian Nuttall (not sponsored to say this; I just find his stuff extremely useful so I wanted to share).