Custom commands allow you to create reusable workflows that can be triggered with a simple / prefix in the chat input box. These commands help standardize processes across your team and make common tasks more efficient.
Commands input example
Commands are currently in beta. The feature and syntax may change as we continue to improve it.

​
How commands work

Commands are defined as plain Markdown files that can be stored in two locations:
  1. Project commands: Stored in the .cursor/commands directory of your project
  2. Global commands: Stored in the ~/.cursor/commands directory in your home directory
When you type / in the chat input box, Cursor will automatically detect and display available commands from both directories, making them instantly accessible across your workflow.

​
Creating commands

  1. Create a .cursor/commands directory in your project root
  2. Add .md files with descriptive names (e.g., review-code.md, write-tests.md)
  3. Write plain Markdown content describing what the command should do
  4. Commands will automatically appear in the chat when you type /
Here’s an example of how your commands directory structure might look: 
.cursor/
└── commands/
    ├── address-github-pr-comments.md
    ├── code-review-checklist.md
    ├── create-pr.md
    ├── light-review-existing-diffs.md
    ├── onboard-new-developer.md
    ├── run-all-tests-and-fix.md
    ├── security-audit.md
    └── setup-new-feature.md

​
Examples

Try these commands in your projects to get a feel for how they work.