inngest-events 是做什麼的？
用於設計事件驅動工作流程、解耦服務、實現扇出模式（一個觸發器，多個下游處理器）、實現具有 ID 的冪等事件處理（24 小時去重窗口），或處理來自 Stripe Webhook 等外部來源的至少一次傳遞。涵蓋 Inngest 事件架構、負載格式、命名慣例、用於冪等性的 ID、ts 參數、扇出模式以及系統事件（如 inngest/function.failed）。
用於設計事件驅動工作流程、解耦服務、實現扇出模式（一個觸發器，多個下游處理器）、實現具有 ID 的冪等事件處理（24 小時去重窗口），或處理來自 Stripe Webhook 等外部來源的至少一次傳遞。涵蓋 Inngest 事件架構、負載格式、命名慣例、用於冪等性的 ID、ts 參數、扇出模式以及系統事件（如 inngest/function.failed）。
Inngest/inngest-events 是專為事件驅動架構設計的開發工具技能，旨在簡化基於 Inngest 平台的事件驅動工作流程、服務解耦及扇出模式的實作。此技能支援開發者設計具備冪等性的事件處理邏輯，透過事件 ID 實現 24 小時重複資料刪除窗口，確保從 Stripe Webhook 等外部來源接收至少一次傳遞的事件時，系統的可靠與一致性。它主要應用於 Inngest 生態系統，涵蓋事件架構定義、負載格式、命名規則、時間戳參數（ts）的使用、扇出模式，以及系統級事件（如 inngest/function.failed）的處理方式。透過遵循此技能提供的指南，開發者能夠建立可擴展、容錯且易於維護的非同步工作流程，有效提升後端服務的靈活性與韌性，特別適合需要精確事件處理與去重的高可靠性場景。
npx skills add https://github.com/inngest/inngest-skills/tree/main/skills/inngest-events用於設計事件驅動工作流程、解耦服務、實現扇出模式（一個觸發器，多個下游處理器）、實現具有 ID 的冪等事件處理（24 小時去重窗口），或處理來自 Stripe Webhook 等外部來源的至少一次傳遞。涵蓋 Inngest 事件架構、負載格式、命名慣例、用於冪等性的 ID、ts 參數、扇出模式以及系統事件（如 inngest/function.failed）。
This repo contains 4 individual skills — each has its own dedicated page.
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.
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.
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.
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.
ElevenLabs text-to-speech with mac-style say UX.
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
Capture and automate macOS UI with the Peekaboo CLI.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".