​
What are Trigger.dev agent rules?

Trigger.dev agent rules are comprehensive instruction sets that guide AI assistants to write optimal Trigger.dev code. These rules ensure your AI assistant understands best practices, current APIs, and recommended patterns when working with Trigger.dev projects.

​
Installation

Install the agent rules with the following command: 
npx trigger.dev@latest install-rules

​
Available rule sets

We provide five specialized rule sets, each optimized for different aspects of Trigger.dev development:
Rule setTokensDescriptionGitHub
Basic tasks1,200Essential rules for writing basic Trigger.dev tasks and fundamental patternsView
Advanced tasks3,000Comprehensive rules for complex workflows, error handling, and advanced task patternsView
Scheduled tasks780Specialized guidance for cron jobs, scheduled workflows, and time-based triggersView
Configuration1,900Complete guide for trigger.config.ts setup, environment configuration, and project structureView
Realtime1,700Using Trigger.dev Realtime features and frontend integration patternsView

​
Claude Code subagent

For Claude Code users, we provide a subagent called trigger-dev-expert that’s an expert at writing well-structured Trigger.dev code.

​
Installation

The subagent is available as an option when running the rules installation command. Select “Claude Code” as your client and choose to include the subagent when prompted. Claude Code subagent installation

​
Usage

Activate the subagent in your prompts by requesting it explicitly: 
use the trigger-dev-expert subagent to create a trigger.dev job that accepts a video url, processes it with ffmpeg to extract the audio, runs the audio through a text-to-speech API like openai, and then uploads both the transcription and the audio to s3
The subagent works best when combined with the appropriate rule sets installed alongside it, providing both high-level architectural guidance and detailed implementation knowledge.

​
Supported AI clients

The Trigger.dev rules work across a wide range of AI coding assistants and editors:
ClientRule activationDocs
CursorAutomatic when working in trigger directoriesLink
Claude CodeContext-aware activation + custom subagentLink
VSCode CopilotIntegration with GitHub Copilot chatLink
WindsurfAutomatic activation in Trigger.dev projectsLink
Gemini CLICommand-line integrationLink
ClineAutomatic context detectionLink
Sourcegraph AMPCode intelligence integrationLink
KiloCustom rule integrationLink
RulerRule managementLink
AGENTS.mdUniversal format for OpenAI Codex, Jules, OpenCode, etc.

​
Rule activation behavior

Different AI tools handle rules differently:
  • Automatic Activation: Cursor, Windsurf, VSCode Copilot, and Cline automatically apply relevant rules when working in Trigger.dev projects or when trigger.config.ts is detected
  • Context-Aware: Claude Code intelligently applies rules based on the current context and file types
  • Manual Integration: AGENTS.md clients and others append rules to configuration files for manual activation

​
Keeping rules updated

Trigger.dev rules are regularly updated to reflect new features, API changes, and best practices. The CLI includes automatic update detection.

​
Automatic update notifications

When running npx trigger.dev@latest dev, you’ll receive notifications when newer rule versions are available with a simple update command.

​
Manual updates

Update rules anytime with: 
npx trigger.dev@latest install-rules
The update process replaces existing rules without creating duplicates, keeping your configuration files clean and organized.

​
Why updates matter

  • Current API patterns: Access the latest Trigger.dev APIs and features
  • Performance optimizations: Benefit from improved patterns and practices
  • Deprecated pattern avoidance: Prevent AI assistants from generating outdated code
  • New feature support: Immediate access to newly released capabilities

​
Getting started

  1. Install the rules:
npx trigger.dev@latest install-rules
  1. Follow the prompts to install the rules for your AI client.
  2. Consider installing the trigger-dev-expert subagent if using Claude Code.

​
Next steps