In this article, I'll be sharing 10 tips I wish I knew when I started using Cursor. From basic to advanced, these tips should help you get the most out of Cursor.
1. Configure VSCode keybindings
You might have noticed that even if you used the VSCode preset when setting up Cursor, the keybindings are not exactly the same. ⌘K related keybindings are remapped to ⌘R and are not easily configurable, so if you're used to using keybindings like ⌘+K U to close unsaved files or ⌘+shift+K to delete a line, you might want to change them.
To be able to change ⌘R related keybindings back to ⌘K, you will first need to change the workbench.action.keychord.leader to ⌘K. After that, you'll be able to set the keybindings to the original ones.
Another option is to use the VSCode Keybindings for Cursor extension.
2. Know each type of AI
| Feature | Description |
|---|---|
autocompletion |
When you start typing, Cursor will suggest completions that you can accept by pressing tab. |
inline chat |
⌘K opens the inline chat. Useful when you only want to edit the current file. |
sidebar chat(Ask) |
⌘L opens the sidebar chat. You can use it for asking questions about specific files or about the whole project. |
sidebar chat(Edit) |
Once in the sidebar chat, you can switch to the "Edit" mode. You can use it for editing multiple files at once. |
sidebar chat(Agent) |
⌘I opens the sidebar chat in agent mode. In this mode, the AI can perform more extensive edits, executing them in multiple steps. It can also detect and fix errors in the IDE, as well as execute terminal commands. This is the most powerful way to use Cursor's AI capabilities. |
terminal chat |
if the focus is on the terminal, ⌘K opens the terminal chat. You tell the AI what you want to do and it will write the commands for you. |
3. Use docs from tools and frameworks
Cursor has a set of docs for many popular tools and frameworks ready to be used by the AI. You can easily add them to the context by typing @Docs.
If you want a doc that is not in the list, You can add a new doc with the @Docs command or you can just type @Web which will make the AI search the web before answering.
Many docs have been adding an /llms.txt page to their website with all the context the AI needs. Here is an example for the turbo.build docs.
4. Reference files or folders
By using @Files you can add a specific file to the AI context.
By using @Folders you can add a whole folder allowing the AI to analyze its contents for answering the prompt.
You can also start typing the file name or folder name directly after @.
You can add all the open files to the context by using the / command inside the chat.
5. Attach images or other files
You can attach design images from Figma or screenshots from other websites that you want Cursor to use as reference.
6. Ignore Files
Cursor automatically ignores all patterns in the .gitignore file.
If there are some files that you are committing to git, but you don't want the AI to care about them, you should add them to the .cursorignore file. (e.g., auto generated files, etc.)
7. Add project rules
You can add project rules by using the ⌘+shift+P > New Cursor Rule command.
You should use it to "teach" the AI about how to do things in your project. (e.g., "Add a new page", "Add an API endpoint", etc.).
These rules can also be useful for when a new member joins the team. They can use these rules to quickly understand project workflows.
For more information on this topic, I highly recommend reading this article: You are using Cursor AI incorrectly...
8. Use MCP tools
You can add MCP tools that gives the agent some special capabilities. For example, by connecting to your development database, the agent will be able to query the database.
Many MCP tools are available. Check out this list for reference: https://github.com/punkpeye/awesome-mcp-servers
9. Yolo Mode
By default, the AI agent will ask for confirmation before executing MCP tools or terminal commands. However, if you enable "Yolo Mode" in Cursor's settings, it can execute them without confirmation. Please use this mode with caution as there is a risk of incorrect operations.
10. Automate the project setup
By having a clear setup guide on the project's README, new members can use the Cursor composer in agent mode to setup the project. The agent can run all the necessary terminal commands to install the dependencies, set up the environment variables, and more.
Conclusion
I've been using Cursor for a few months now, and I've been enjoying it a lot. I hope you learned some new tips you didn't know before.
If you have any other tips, please share them in the comments.
Happy coding!
