while using cursor, I figure that a lot of times I am struggling to steer it to do things correctly. I would like a system the can continue to improve itself.
What I am currently doing and successful, is the write a project rule saying it must read two docs/developement_guide.md and docs/learn_from_error.md. whenever it starts a chat. Also after a iteration, when it achieves something or corrected an error, it should write the experience into those two files.
This feed back system worked well and I have a more and more useful guide int the docs folder. I found that my project is self-evolving and cursor becomes more predictable.
I usually use Claude 4 sonnet (thinking).
Often it will create/update a Readme.md file on the section I was working with.
I assume it’s including this since it’s already in the project workspace.
Unfortunately it won’t always look in the files I specify in the rules.
For instance, I periodically copy the server code to the client machine. This is clearly stated in the rules as a place to look for context. It doesn’t always look there until I tell it “Check the rules”.
One thing that helps is while it’s thinking or writing code, I’ll just talk to it to give it ideas that might help. This seems to help.
** Use `dev_util.sh` as your primary development tool. **
** See `dev_util.guide.md` for complete usage instructions and best practices. **
** See docs/development_guide.md for project information and development guidance. **
** See docs/learn_from_error.md for experiences of errors and corrections, so that you don't make the same mistake **
** When a new chat is started, read dev_util.guide.md , docs/development_guide.md and docs/learn_from_error.md first. **
** After a development cycle, if you corrected mistakes or gained important insight that may help future development, you should update docs/development_guide.md or docs/learn_from_error.md to save the knowledge. (These files are there to benefit future developements, don't record history that is not going to be useful for future developement)
** Don't ever modify dev_util.guide.md, it is a generated file. It is just there for your information **
sometimes, I will have to explicitly say: “update the guides” after some bug fixes or long running. If I have a really long chat, I will have to say: “read project rules again” since the information might be squeezed out of context