Community生產力與協作github.com

inngest/inngest-steps

在需要實現延遲(例如24小時購物車放棄通知、排程跟進)、等待人工審核或帶超時的外部事件(審查關卡、Webhook回調、非同步API完成)、輪詢外部服務而不因崩潰遺失狀態、呼叫其他函數並等待結果、記憶化昂貴運算以免重試時重複執行,或在工作流程中並行執行非同步工作時使用。涵蓋Inngest步驟方法:step.run, step.sleep, step.waitForEvent, step.waitForSignal, step.sendEvent, step.invoke, step.ai,以及循環和並行執行模式。

inngest-steps 是什麼?

此技能旨在協助開發者利用Inngest步驟方法(step.run, step.sleep, step.waitForEvent, step.waitForSignal, step.sendEvent, step.invoke, step.ai)構建具備彈性與持久性的工作流程。它特別適合需要跨進程重啟仍能保持狀態的延遲操作(如24小時購物車放棄通知)、等待人工審批或外部事件(帶超時機制的審查關卡或Webhook回調)、從外部服務安全輪詢(即使崩潰也不遺失狀態),以及呼叫其他函數並等待其結果等場景。此外,該技能支援昂貴運算的記憶化(避免重試時重複執行),並提供循環與並行執行模式,以最佳化工作流程效率。支援所有Inngest平台,並於步驟程式中保持狀態一致性。

相容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/inngest/inngest-skills/tree/main/skills/inngest-steps

Installed? Explore more 生產力與協作 skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

inngest-steps 是做什麼的?

在需要實現延遲(例如24小時購物車放棄通知、排程跟進)、等待人工審核或帶超時的外部事件(審查關卡、Webhook回調、非同步API完成)、輪詢外部服務而不因崩潰遺失狀態、呼叫其他函數並等待結果、記憶化昂貴運算以免重試時重複執行,或在工作流程中並行執行非同步工作時使用。涵蓋Inngest步驟方法:step.run、step.sleep、step.waitForEvent、step.waitForSignal、step.sendEvent、step.invoke、step.ai,以及循環和並行執行模式。

Individual skills in this repo

This repo contains 4 individual skills — each has its own dedicated page.

inngest/inngest-durable-functions

Use when building functions that must survive process crashes, retry automatically on failure, run on a schedule, react to events, or maintain state across infrastructure failures — e.g., webhook handlers that drop events, flaky cron jobs, background jobs that fail mid-execution, or workflows that need to resume where they left off. Covers Inngest function configuration, triggers (events, cron, invoke), step execution and memoization, idempotency, cancellation, error handling, retries, logging, and observability.

inngest/inngest-events

Use when designing event-driven workflows, decoupling services, implementing fan-out patterns (one trigger, many downstream handlers), implementing idempotent event handling with IDs (24-hour dedupe window), or handling at-least-once delivery from external sources like Stripe webhooks. Covers Inngest event schema, payload format, naming conventions, IDs for idempotency, the ts param, fan-out patterns, and system events like inngest/function.failed.

inngest/inngest-middleware

Use when adding cross-cutting concerns to durable functions — structured logging or tracing across all functions, error tracking with Sentry, payload encryption for sensitive data, dependency injection of clients (DB, Stripe, etc.) into function handlers, custom telemetry, or behavior that should apply uniformly across many functions. Covers Inngest middleware lifecycle, creating custom middleware, dependencyInjectionMiddleware, @inngest/middleware-encryption, @inngest/middleware-sentry, and custom middleware patterns.

inngest/inngest-setup

Use when adding durable execution to a TypeScript project — building retry-safe webhook handlers, background jobs that survive crashes, scheduled tasks, or long-running workflows that outlive a single request. Covers Inngest SDK installation, client config, environment variables, serve endpoints (Next.js, Express, Hono, Fastify), connect-as-worker mode, and the local dev server.

相關技能