adding a few tips I have after playing sometime with cursor.
1. do commit frequently, recommend to do commit for every big change(a new feature such as a new button added for some function, some big UI change like added some new component changing the UI layout a bit)
2. test everything(regression testing) after doing big change with cursor, it may affect existing functions when adding new features you think should not impact other parts
3. if trying to add a new complete feature including changes to multiple places(fe, be etc), please using Composer instead of Chat
4. when working with UI changes(fe), be careful of needing forth and back of changes. one recommendation is you write the skeleton yourself, then ask cursor to fill in the missing components.
5. when giving instructions, use bullet points and state clearly about the requirements(write the step-by-step instructions) would have better result.
In my .cursorrules I have instructions that after every testable change it should ask me to test it, and if I say it's good it should commit.
So I ask for some feature, it implements, I test and either give feedback or simply say "good" or "that works" in which case it'll produce a commit command I can just press Run on. Makes it very easy to commit constantly.
Also I use Composer exclusively over Chat and have zero hesitation to hit those restore buttons if anything went down the wrong path.
1. do commit frequently, recommend to do commit for every big change(a new feature such as a new button added for some function, some big UI change like added some new component changing the UI layout a bit)
2. test everything(regression testing) after doing big change with cursor, it may affect existing functions when adding new features you think should not impact other parts
3. if trying to add a new complete feature including changes to multiple places(fe, be etc), please using Composer instead of Chat
4. when working with UI changes(fe), be careful of needing forth and back of changes. one recommendation is you write the skeleton yourself, then ask cursor to fill in the missing components.
5. when giving instructions, use bullet points and state clearly about the requirements(write the step-by-step instructions) would have better result.
These tips are based on working with one side project(was trying to test cursor's capability): https://www.pixelstech.net/application/sudoku