vercel/workflow

workflow-init

Install and configure Vercel Workflow SDK before it exists in nodemodules.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/vercel/workflow --skill workflow-init

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

workflow-init

Initial setup of Vercel Workflow SDK before workflow is installed. Fetch the official getting-started guide for the user's framework.

Decision flow

0) Sanity check

Read package.json. If workflow is already a dependency, tell the user to use /workflow instead (it reads versioned docs from node_modules/workflow/docs/). Only continue if workflow is missing.

1) Determine the framework

Non-interactive: If the user named a framework in their prompt, use it directly.

Auto-detect: Inspect package.json deps and config files. Use the first match:

  1. Next.js - next dep or next.config.*
  2. Nuxt - nuxt dep or nuxt.config.*
  3. SvelteKit - @sveltejs/kit dep or svelte.config.*
  4. Astro - astro dep or astro.config.*
  5. NestJS - @nestjs/core dep or nest-cli.json
  6. Nitro - nitro dep or nitro.config.*
  7. Express - express dep
  8. Fastify - fastify dep
  9. Hono - hono dep
  10. Vite - vite dep (and not matched above)

If no match or multiple matches, ask the user to pick.

2) Fetch and follow the getting-started guide

Fetch exactly one of these URLs and follow the guide step-by-step:

FrameworkURL
Next.jshttps://workflow-sdk.dev/docs/getting-started/next
Expresshttps://workflow-sdk.dev/docs/getting-started/express
Honohttps://workflow-sdk.dev/docs/getting-started/hono
Fastifyhttps://workflow-sdk.dev/docs/getting-started/fastify
NestJShttps://workflow-sdk.dev/docs/getting-started/nestjs
Nitrohttps://workflow-sdk.dev/docs/getting-started/nitro
Nuxthttps://workflow-sdk.dev/docs/getting-started/nuxt
Astrohttps://workflow-sdk.dev/docs/getting-started/astro
SvelteKithttps://workflow-sdk.dev/docs/getting-started/sveltekit
Vitehttps://workflow-sdk.dev/docs/getting-started/vite

Each guide covers: install deps, configure framework, create first workflow, create route handler, run + verify.

3) Verify setup

  • Start the dev server per the guide.
  • Trigger the example endpoint with the provided curl.
  • Confirm logs show the workflow and steps executing.
  • Optional: npx workflow web or npx workflow inspect runs.

4) No framework yet?

If no framework exists, ask what the user wants:

  • Web app: Next.js / Nuxt / SvelteKit / Astro
  • API server: Express / Fastify / Hono
  • Minimal server: Nitro or Vite

Then follow the "Create Your Project" section of the chosen guide.

Concept questions (pre-install)

If the user asks conceptual questions before installing, fetch:

  • https://workflow-sdk.dev/docs/foundations/workflows-and-steps
  • https://workflow-sdk.dev/cookbook

Handoff

When setup is complete, tell the user: Use `/workflow` for ongoing development - it reads the versioned docs bundled in node_modules/workflow/docs/.

Correlati per attività

dallo stesso repository

Altri Skills

Tutti gli Skills
vercel
Ufficiale

migrating-to-workflow-sdk

Migrates Temporal, Inngest, Trigger.dev, and AWS Step Functions workflows to the Workflow SDK. Use when porting Activities, Workers, Signals, step.run(), step.waitForEvent(), Trigger.dev tasks / wait.forToken / triggerAndWait, ASL JSON state machines, Task/Choice/Wait/Parallel states, task tokens, or child workflows. For Inngest, runs the workflow migrate inngest codemod first and finishes what it leaves as TODOs.

Installazioni / 1h
1
GitHub Stars
2,5K
Aggiornato
21 nov
vercel
Ufficiale

workflow

Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow sdk", "queue", "event", "push", "subscribe", or step-based orchestration.

Installazioni / 1h
2
GitHub Stars
2,5K
Aggiornato
21 nov
vercel
Ufficiale

internal-dev-workbench

Spin up a portless + tmux dev session for the Workflow SDK that gives each git worktree isolated . .localhost URLs for the Next.js workbench and the observability UI, plus a Claude statusline that surfaces those URLs. Use only when the user asks for a "portless dev session", a "tmux dev layout for workflow", "worktree-isolated dev URLs", or wants to wire workflow dev URLs into the Claude statusline. Do not activate for the generic "start the dev server" / "run pnpm dev" task.

Installazioni / 1h
2
GitHub Stars
2,4K
Aggiornato
13 set
vercel
Ufficiale

migrating-workflow-v4-to-v5

- Upgrades an app from Workflow SDK 4.x to 5.0. Use when bumping the workflow / @workflow/ dependencies to v5, or when hitting removed v4 APIs — runStep, stepEntrypoint, workflow/internal/private, @workflow/core/private, writeToStream / closeStream / readFromStream on a World, world.steps.get without a runId, hook.getConflict() returning { runId }, hook.metadata read synchronously off a getHookByToken() result, experimentalsetAttributes, createLocalWorld / createVercelWorld, NestLocalBuilder imp

Installazioni / 1h
2
GitHub Stars
2,4K
Aggiornato
13 set