4 ms·
Amazing Two things I would add: 1. Use git and commit changes (very) frequently. Often the AI makes a recommendation that looks good, but has consequences 4
by Ashbt 2y ago
Amazing
Two things I would add:
1. Use git and commit changes (very) frequently.
Often the AI makes a recommendation that looks good, but has consequences 4 or 5 changes later that you'll need to reckon with. You'll see this especially with web vs. mobile UI behaviours. Cursor isn't so good at reverting changes yet, and GIT has saved me a LOT of headache.
2. Collaborate with o1 to create a PRD and put it in the same folder as your specs.
This increases the likelihood Cursor's recommended changes comply with your intent, style and color guidelines and overall project direction.
- Kiro 2y agoIf you're using Cursor Composer it's very easy to jump back at any time in the history using "Revert all files to before this message". I use it all the time and have stopped obsessively committing every change as a result.
- victor106 2y ago> 2. Collaborate with o1 to create a PRD what is a PRD?
- debo_ 2y ago"Product Requirements Document," I think. A high-level specification of what the thing should do and why.