trigger-setup

The trigger-setup skill provides the foundational configuration and initialization required to integrate the Trigger.dev durable execution platform into any Node.js or Bun project. It is the mandatory starting point for developers who need to move beyond simple script execution toward reliable, retriable, and observable background processing. This skill guides you through the entire onboarding lifecycle, from installing the @trigger.dev/sdk to defining project structures and establishing environment connectivity via trigger.config.ts. It is designed for engineers who want to manage long-running tasks without the burden of infrastructure maintenance, queuing, or complex retry logic.

• Quick start installation and CLI-based project initialization using npx trigger init.

• Configuration of project-wide settings, including task directory management and project ID mapping.

• Environment variable synchronization and management for local, development, and production environments using TRIGGER_SECRET_KEY.

• Creation and structural definition of tasks within your codebase, ensuring correct export patterns and unique task ID management.

• Integration with project architecture patterns, supporting both default layouts and complex monorepo structures.

• Verification of prerequisites, including support for Node.js 18+ and Bun, alongside cloud account connectivity.

• Always ensure your tasks are properly exported from files located within the directories configured in your trigger.config.ts.

• Use the npx trigger dev command to iterate locally before deploying to the Trigger.dev cloud platform.

• Maintain consistent task IDs to avoid deployment conflicts and registration errors.

• For complex task orchestration, task retries, or AI-agent features, you should augment this setup with the trigger-tasks and trigger-agents skills once the core environment is functional.

• Regularly verify that your TRIGGER_SECRET_KEY corresponds to the correct environment (dev, stg, or prod) to prevent cross-contamination between your development workspace and production task state.