Trigger.dev

# MISSION: Scaffold "Trigger.dev" Production Architecture
You are an expert Senior Staff Software Architect and Full-Stack Engineer. Your mission is to scaffold and implement a production-grade, highly reliable, and modular codebase following the proven architecture of **Trigger.dev**.
---
## 1. PROJECT SPECIFICATIONS & BENCHMARK
- **Reference Architecture**: Trigger.dev
- **What It Does**: Open-source developer platform for building and deploying durable background jobs, AI agent workflows, and scheduled tasks in TypeScript.
- **Domain & Category**: Job Queue / Dev Tool
- **Production Scale**: 6-20 people
- **Development Mode**: HYBRID
- **Architectural Rationale**: Trigger.dev eliminates serverless timeout restrictions and queue boilerplate by providing durable, resumable TypeScript workflows.
- **Live Website Reference**: https://trigger.dev
- **Source Repository**: https://github.com/triggerdotdev/trigger.dev
---
## 2. PRODUCTION TECH STACK
- **Full Stack Array**: TypeScript, Remix, Prisma, PostgreSQL, ClickHouse, Redis, Docker, Turborepo
- **Primary Language(s)**: TypeScript, JavaScript, Shell, CSS, ANTLR, Go Template
- **License of the reference repo**: Apache-2.0
- **Frontend**: Remix — Web application dashboard providing run inspectors, logs, and billing management
- **Backend & APIs**: TypeScript — Primary language powering execution engines, SDK packages, and supervisor daemons
- **Data & persistence**: Prisma — Type-safe database client and migration manager for primary PostgreSQL schemas; PostgreSQL — Primary relational database storing accounts, organizations, environments, and runs; ClickHouse — Columnar analytics database storing execution traces, logs, and telemetry spans; Redis — Distributed queues, task rate-limiting, and run state coordination via Redlock
- **Infrastructure & deploy**: Docker — Containerized task environments and multi-service development infrastructure; Turborepo — Monorepo build orchestrator caching package builds and testing pipelines
---
## 3. KEY ARCHITECTURAL DECISIONS (audited from https://github.com/triggerdotdev/trigger.dev @ 8067b1f)
1. **Decoupled Run Engine with Distributed Redis Queues**: Separates task queueing and execution scheduling into an independent run-engine package backed by Redis streams and Redlock concurrency guards.
2. **Hybrid Database Architecture with PostgreSQL and ClickHouse**: Uses PostgreSQL via Prisma for transactional entity states while offloading massive timeseries run logs and OpenTelemetry spans to ClickHouse.
3. **Containerized Task Supervision Daemon**: Implements apps/supervisor to manage ephemeral Node.js and Bun worker containers over Dockerode and Kubernetes client APIs.
4. **Realtime Checkpointing and Waitpoints**: Enables long-running workflows to pause execution without consuming CPU, resuming automatically on external webhooks or schedule timeouts.
---
## 4. NON-NEGOTIABLE ARCHITECTURAL GUARDRAILS
1. **Monorepo & Modular Separation**:
   - Structure as a Turborepo monorepo with strict package boundaries:
     - `apps/web`: Application UI, routing, layouts, and server endpoints.
     - `packages/ui`: Shared design tokens, CSS variables, and Radix UI primitive components.
     - `packages/db`: Database schemas, client singleton, declarative migrations, and seed scripts.
     - `packages/config`: Shared TypeScript, ESLint, and build configurations.
2. **Strict Type Safety & Zero `any` Policy**:
   - Enable `strict: true`, `noImplicitAny: true`, and `strictNullChecks: true`.
   - Validate ALL external inputs, API request bodies, and query parameters with **Zod** schemas before execution.
3. **Frontend & Rendering Guidelines**:
   - Isolate interactive UI state to leaf components. Keep core pages lightweight and performant.
4. **Design System & Aesthetics**:
   - Keep every color, radius, shadow and font in a single token file (CSS variables) and consume tokens everywhere; never hardcode hex values in components.
   - Prefer crisp 1px borders and one subtle shadow scale over blurry default shadows. Pair one sans-serif for body/headings with one monospace for tags, badges, metrics, and code.
5. **Data Layer & Reliability**:
   - Write declarative schema definitions with foreign keys, composite indexes on queried filters, and automated timestamp triggers.
   - Use connection pooling and prepared statements for serverless database execution.
---
## 5. STEP-BY-STEP SCAFFOLDING ROADMAP
- **Phase 1: Workspace & Root Config**: Initialize package manager, monorepo configuration (`turbo.json`, `tsconfig.base.json`, `package.json`).
- **Phase 2: Database Schema & Client**: Set up the data layer (Prisma, PostgreSQL, ClickHouse, Redis): client, connection pool, models, and migration scripts.
- **Phase 3: Design Tokens & UI Primitives**: Build accessible `Button`, `Input`, `Card`, `Badge`, and layout wrappers inside `packages/ui`.
- **Phase 4: Core Application Routes & Handlers**: Implement primary authentication, user session handling, and application routes.
- **Phase 5: Quality Assurance & Build Verification**: Run `tsc --noEmit`, ESLint, Prettier, and smoke test suites to ensure zero compilation or runtime errors.
---
## 6. EXECUTION INSTRUCTIONS
1. Review all specifications, architectural guardrails, and stack choices above.
2. Present the full monorepo directory tree structure.
3. Systematically generate the complete, production-ready codebase according to the 5-phase roadmap above — starting with the root workspace setup, followed by the database schema, UI design system package, and full-stack application routes until the repository is fully scaffolded and ready to run.