Co-founder, Trigger.dev
Cursor has become the go-to AI coding assistant for many developers, and with good reason. Adding custom rules to Cursor helps you code faster by giving the AI context about your project. Now, writing Trigger.dev tasks should mean fewer trips to the docs with our comprehensive Cursor rules.
What these rules help you do
These Cursor rules are specifically designed to help you write Trigger.dev tasks correctly. Here's what they do and don't cover:
| Helps with | Don't use it for |
|---|---|
| Creating basic tasks | Deploying |
| Creating scheduled tasks | Project setup |
| Creating schema tasks | Infrastructure configuration |
| Triggering tasks from backend | API keys |
| Task lifecycle functions | Using tags |
| Using Realtime | |
| Idempotency patterns | |
| Metadata handling | |
| Using build extensions |
How to install Cursor rules
- Locate the
.cursor/rulesfolder in your project root - Download the writing-tasks.mdc file and place it in the
.cursor/rulesfolder - For more help installing Cursor rules, see Cursor's docs
Tips for making the most of Cursor rules
-
Turn on Yolo mode in Cursor settings. This sounds scary, but it just means Cursor will act more like an agent that checks for errors, fixes them, runs commands to install packages, and won't stop until the code is error-free and running. Obviously, worth checking the changes to make sure you're happy.
-
Explicitly add context when needed - Cursor should know when to use the rules file, but I recommend selecting it from the "@ Add context" button above the prompt window. Then select "Cursor Rules" and select your rules file.
-
Check out Steve's tweet from Builder.io for more tips and tricks on how he uses Cursor.
New to Trigger.dev?
- Create a Trigger.dev account at cloud.trigger.dev
- Follow the quick start guide to install Trigger
- Download the cursor rules file
If you find anything missing or if it generates incorrect code, let me know! We'll keep these rules updated to be as useful as possible.