internal-dev-workbench
Spin up a portless + tmux dev session for the Workflow SDK that gives each git worktree isolated `<branch>.<name>.localhost` URLs for the Next.js workbench and…
Install and configure Vercel Workflow SDK before it exists in node_modules. Use when the user asks to "install workflow", "set up workflow", "add durable workflows", "configure workflow sdk", or "init workflow" for Next.js, Express, Hono, Fastify, NestJS, Nitro, Nuxt, Astro,
$ npx -y skills add vercel/workflow --skill workflow-init --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/workflow-initContext preview
The summary Claude sees to decide when to auto-load this skill.
Install and configure Vercel Workflow SDK before it exists in node_modules. Use when the user asks to "install workflow", "set up workflow", "add durable workflows", "configure workflow sdk", or "init workflow" for Next.js, Express, Hono, Fastify, NestJS, Nitro, Nuxt, Astro,
name: workflow-init description: Install and configure Vercel Workflow SDK before it exists in node_modules. Use when the user asks to "install workflow", "set up workflow", "add durable workflows", "configure workflow sdk", or "init workflow" for Next.js, Express, Hono, Fastify, NestJS, Nitro, Nuxt, Astro, SvelteKit, or Vite. metadata: author: Vercel Inc. version: '1.4'
Initial setup of Vercel Workflow SDK **before** `workflow` is installed. Fetch the official getting-started guide for the user's framework.
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.
**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.
Fetch **exactly one** of these URLs and follow the guide step-by-step:
| Framework | URL | |-----------|-----| | Next.js | https://workflow-sdk.dev/docs/getting-started/next | | Express | https://workflow-sdk.dev/docs/getting-started/express | | Hono | https://workflow-sdk.dev/docs/getting-started/hono | | Fastify | https://workflow-sdk.dev/docs/getting-started/fastify | | NestJS | https://workflow-sdk.dev/docs/getting-started/nestjs | | Nitro | https://workflow-sdk.dev/docs/getting-started/nitro | | Nuxt | https://workflow-sdk.dev/docs/getting-started/nuxt | | Astro | https://workflow-sdk.dev/docs/getting-started/astro | | SvelteKit | https://workflow-sdk.dev/docs/getting-started/sveltekit | | Vite | https://workflow-sdk.dev/docs/getting-started/vite |
Each guide covers: install deps, configure framework, create first workflow, create route handler, run + verify.
If no framework exists, ask what the user wants:
Then follow the "Create Your Project" section of the chosen guide.
If the user asks conceptual questions before installing, fetch:
When setup is complete, tell the user: **Use `/workflow` for ongoing development** - it reads the versioned docs bundled in `node_modules/workflow/docs/`.
Workflow SDK: Build durable, reliable, and observable apps and AI Agents in TypeScript
Repo: vercel/workflow
Spin up a portless + tmux dev session for the Workflow SDK that gives each git worktree isolated `<branch>.<name>.localhost` URLs for the Next.js workbench and…
Migrates Temporal, Inngest, Trigger.dev, and AWS Step Functions workflows to the Workflow SDK. Use when porting Activities, Workers, Signals, step.run(),…
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`,…
Upgrades a custom Workflow SDK World implementation from the v4 spec to v5. Use when a package implements the `World` interface from `@workflow/world` and is…
Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry…