Community生產力與協作github.com

inngest/inngest-setup

用於為 TypeScript 專案添加持久化執行能力 — 建立可重試的安全 Webhook 處理器、能在崩潰後存活的背景任務、排程任務,或超出單一請求生命週期的長期工作流程。涵蓋 Inngest SDK 安裝、客戶端設定、環境變數、服務端點(Next.js、Express、Hono、Fastify)、connect-as-worker 模式以及本機開發伺服器。

inngest-setup 是什麼?

此技能專為需要在 TypeScript 專案中整合持久化執行(Durable Execution)的開發者設計,特別適合建構高可靠性的後端系統。它涵蓋了完整的 Inngest SDK 設定流程,從安裝、客戶端配置到環境變數管理,並支援多種主流框架的服務端點,包括 Next.js、Express、Hono 和 Fastify。此外,此技能也詳細說明了 connect-as-worker 模式,讓應用程式能以工作者身分連接到 Inngest 平台,以及如何啟動本機開發伺服器進行測試。透過此技能,開發者可以快速建立能夠自動重試失敗任務、在伺服器崩潰後恢復執行的背景工作與排程任務,顯著提升應用程式的穩定性與可維護性,無需手動處理複雜的基礎設施細節。

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

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

在你喜歡的 AI 中提問

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

說明文件

inngest-setup 是做什麼的?

用於為 TypeScript 專案添加持久化執行能力 — 建立可重試的安全 Webhook 處理器、能在崩潰後存活的背景任務、排程任務,或超出單一請求生命週期的長期工作流程。涵蓋 Inngest SDK 安裝、客戶端設定、環境變數、服務端點(Next.js、Express、Hono、Fastify)、connect-as-worker 模式以及本機開發伺服器。

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-steps

Use when implementing delays that must survive process restarts (e.g., 24-hour cart abandonment, scheduled follow-ups), waiting for human approval or external events with timeouts (review gates, webhook callbacks, async API completion), polling external services without losing state on crashes, calling other functions and awaiting their results, memoizing expensive operations so they don't re-run on retry, or running async work in parallel inside a workflow. Covers Inngest step methods: step.run, step.sleep, step.waitForEvent, step.waitForSignal, step.sendEvent, step.invoke, step.ai, plus patterns for loops and parallel execution.

相關技能