trigger-getting-startedlisted

Bootstrap Trigger.dev into an existing project from scratch: authenticate the CLI, install @trigger.dev/sdk and @trigger.dev/build, write trigger.config.ts with the project ref and task dirs, scaffold a /trigger directory with a first task, wire tsconfig and .gitignore, set TRIGGER_SECRET_KEY, and run the dev server. Load this when a project has no trigger.config.ts yet and the user asks to "add Trigger.dev", "set up Trigger.dev", "initialize Trigger.dev", or get a first task running, including in a monorepo. Once the project is set up and you are writing task code, switch to the trigger-authoring-tasks skill.
nateruze/system_architecture_builder · ★ 0 · AI & Automation · score 63

Install: claude install-skill nateruze/system_architecture_builder

# Getting started with Trigger.dev Set up Trigger.dev in an existing project. The end state is: the SDK installed, a `trigger.config.ts` pointing at a project ref, a `/trigger` directory with at least one exported task, and `trigger dev` running so the task shows up in the dashboard. The fastest path is the CLI's own wizard, which performs every mechanical step below and also offers to install the MCP server and these agent skills: ```bash npx trigger.dev@4.5.8 init ``` Prefer `init` when you can. Do the manual steps further down when `init` does not fit (monorepos, an existing config to extend, or a non-interactive environment). ## Two steps need the human Most of setup is automatable, but two steps require a person and cannot be done headlessly. When you reach them, stop and ask the user to do them, then continue: 1. **Authenticating the CLI.** `npx trigger.dev@4.5.8 login` opens a browser for the user to sign in. If they have no account, point them to https://cloud.trigger.dev (or a self-hosted instance) first. You cannot complete this for them. 2. **The secret key and project ref.** `TRIGGER_SECRET_KEY` and the project ref (`proj_...`) come from the dashboard. Ask the user to copy the **DEV** secret key from the project's API Keys page, and to pick or create the project so you have its ref. `trigger init` can select the project interactively once the user is logged in. Treat these as handoffs: state exactly what you need, wait for the user, then res