Menú
Trigger.dev v3 background jobs in this monorepo. Use when editing Trigger tasks, calling tasks.trigger, trigger.config.ts, HARMONIA_TRIGGER_* env vars, or pipeline stage subtasks.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Better Auth integration for Next.js (App Router) with Drizzle adapter. Use when connecting to Better Auth, configuring OAuth providers, or implementing protected routes with middleware.
Enforce CI pipeline conventions for your application. Use when adding CI checks, modifying GitHub Actions workflows, discussing CI vs deployment, or working with scripts/ci.sh. Prevents deployment steps in CI and ensures the extensible step pattern is followed.
Complete Drizzle ORM documentation in markdown format. Use when working with Drizzle ORM - covers schema definition, queries, migrations, database connections (PostgreSQL, MySQL, SQLite), integrations (Neon, Supabase, PlanetScale, Cloudflare D1, Turso), column types, relations, transactions, and framework usage (Next.js, SvelteKit, Astro).
Complete Drizzle ORM documentation in markdown format. Use when working with Drizzle ORM - covers schema definition, queries, migrations, database connections (PostgreSQL, MySQL, SQLite), integrations (Neon, Supabase, PlanetScale, Cloudflare D1, Turso), column types, relations, transactions, and framework usage (Next.js, SvelteKit, Astro).
Triage CI failures and PR review comments using scripts/pr-status.js. Use when investigating failing CI jobs, flaky tests, or PR review feedback. Covers blocker-first prioritization (build > lint > types > tests), CI env var matching for local reproduction, and the Known Flaky Tests distinction.
Master TanStack Query (React Query) v5 for server state management in React applications. Use when fetching data from APIs, managing server state, caching, or handling mutations. Triggers on phrases like "react query", "tanstack query", "data fetching", "cache management", "server state", or file patterns like *query*.ts, *Query*.tsx, queryClient.ts.
| name | trigger-dev |
| description | Trigger.dev v3 background jobs in this monorepo. Use when editing Trigger tasks, calling tasks.trigger, trigger.config.ts, HARMONIA_TRIGGER_* env vars, or pipeline stage subtasks. |
Background work runs on Trigger.dev v3. Do not use Inngest patterns here; tasks are defined with @trigger.dev/sdk and executed via *.trigger().
apps/api/trigger.config.ts — project ref (HARMONIA_TRIGGER_PROJECT_REF), task directories, retries.packages/common/src/trigger/tasks/ — task implementations (e.g. organize pipeline and per-stage children).HARMONIA_TRIGGER_SECRET_KEY — API secret (validated in @harmonia/env for the API preset).HARMONIA_TRIGGER_PROJECT_REF — project slug/ref from the Trigger dashboard.Local CLI expects TRIGGER_SECRET_KEY / TRIGGER_PROJECT_REF; pnpm trigger:dev loads root .env and maps from the HARMONIA_* names when the legacy vars are unset (scripts/run-trigger-dev.mjs).
runId / userId payload so ORPC and cron enqueue paths stay aligned with pipeline_run rows.failed so nothing stays stuck in running.