inngest-events 是做什么的？
用于设计事件驱动的工作流，解耦服务，实现扇出模式（一个触发，多个下游处理器），通过 ID 实现幂等事件处理（24 小时去重窗口），或处理来自 Stripe 等外部源的至少一次交付。涵盖 Inngest 事件模式、负载格式、命名约定、幂等 ID、ts 参数、扇出模式以及系统事件（如 inngest/function.failed）。
用于设计事件驱动的工作流，解耦服务，实现扇出模式（一个触发，多个下游处理器），通过 ID 实现幂等事件处理（24 小时去重窗口），或处理来自 Stripe 等外部源的至少一次交付。涵盖 Inngest 事件模式、负载格式、命名约定、幂等 ID、ts 参数、扇出模式以及系统事件（如 inngest/function.failed）。
该技能旨在指导开发者利用 Inngest 平台设计、实现事件驱动的工作流，并解决分布式系统中的常见挑战。它强调了如何通过事件模式来解耦服务，实现一个事件触发多个下游处理器的扇出模式，并解释了如何利用事件 ID 实现 24 小时内的幂等性处理，确保外部源（如 Stripe Webhooks）的至少一次交付不会产生重复副作用。 技能详细介绍了 Inngest 事件的完整模式，包括 payload 格式、命名约定、用于幂等性的 ID 字段、时间戳（ts）参数以及扇出模式的最佳实践。此外，还涵盖了系统事件（如 inngest/function.failed），帮助开发者处理函数失败等异常情况。该技能适用于 Inngest 平台，并为开发者提供了构建可靠、可扩展事件驱动系统的核心知识。
npx skills add https://github.com/inngest/inngest-skills/tree/main/skills/inngest-events用于设计事件驱动的工作流，解耦服务，实现扇出模式（一个触发，多个下游处理器），通过 ID 实现幂等事件处理（24 小时去重窗口），或处理来自 Stripe 等外部源的至少一次交付。涵盖 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".