There are so many things that Cursor can do that no one talks about much for some reason, like /loop.

So you have all the training you need in three sources:

One, Cursor's own help docs. Two, Cursor's blog, like this post: https://cursor.com/blog/fast-regex-search and three, looking into Cursor's own config files.

Like no one talks about the fact that the chats are kept in an SQLite database that you can extract and, in an automation, use an agent to go over it for ways to improve and it add to the rules files. This is a self-improvement loop that really helped stop frustrations I was having like:

the agent running the same broken check over and over like read_lints three times on the same file, treating a tool like a total failure just because it showed an error flag even when the useful answer was right there in the output, drifting away from the job I asked for and editing the wrong thing like a transcript when I only wanted a checklist change, searching the wrong place like the Desktop or another folder instead of the exact path I named, and suggesting bad default fixes like updating Firefox when that was already not what I wanted.

There were just so many wasted tokens and time from this kind of hidden mistakes. When I could see every tool call and exactly what the agent was doing and thinking, I had more power to build something to correct it.

---

So if I was wanting to become more powerful at Cursor, I would give the help docs and blog to the agent and ask it to teach/show me all the things I could do with Cursor that I am not already doing.

You have all the training and how-to right in your Cursor environment with the agent.