Communitygithub.com

inngest/inngest-events

Útil al diseñar flujos de trabajo basados en eventos, desacoplar servicios, implementar patrones de difusión (fan-out: un disparador, múltiples controladores posteriores), manejar eventos idempotentes con IDs (ventana de desduplicación de 24 horas) o gestionar entrega al menos una vez desde fuentes externas como webhooks de Stripe. Cubre el esquema de eventos de Inngest, formato de carga útil, convenciones de nombres, IDs para idempotencia, el parámetro ts, patrones de difusión y eventos del sistema como inngest/function.failed.

¿Qué es inngest-events?

El skill inngest/inngest-events proporciona una guía completa para diseñar flujos de trabajo basados en eventos con Inngest, una plataforma para construir sistemas distribuidos y desacoplados. Es especialmente útil cuando necesitas desacoplar servicios, implementar patrones de difusión (fan-out) donde un solo evento dispara múltiples funciones, manejar eventos idempotentes usando IDs con una ventana de desduplicación de 24 horas, o garantizar la entrega al menos una vez desde fuentes externas como webhooks de Stripe. El skill cubre en detalle el esquema de eventos de Inngest, el formato de carga útil (payload), las convenciones de nombres, el uso del parámetro `ts` para marcas de tiempo, y los eventos del sistema como `inngest/function.failed`. Está diseñado para usarse con agentes de IA como Claude Code y asiste a desarrolladores en la creación de workflows robustos, predecibles y escalables, minimizando errores y promoviendo buenas prácticas en la arquitectura orientada a eventos.

Compatible con~Claude Code~Codex CLI~Cursor
Part ofDesign & UI
npx skills add https://github.com/inngest/inngest-skills/tree/main/skills/inngest-events
Ver original→Ver todas las habilidades

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

Documentación

¿Qué hace inngest-events?

Útil al diseñar flujos de trabajo basados en eventos, desacoplar servicios, implementar patrones de difusión (fan-out: un disparador, múltiples controladores posteriores), manejar eventos idempotentes con IDs (ventana de desduplicación de 24 horas) o gestionar entrega al menos una vez desde fuentes externas como webhooks de Stripe. Cubre el esquema de eventos de Inngest, formato de carga útil, convenciones de nombres, IDs para idempotencia, el parámetro ts, patrones de difusión y eventos del sistema como inngest/function.failed.

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

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.

Skills relacionados

steipete/sag

ElevenLabs text-to-speech with mac-style say UX.

community

steipete/oracle

Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.

community

steipete/peekaboo

Capture and automate macOS UI with the Peekaboo CLI.

community

mattpocock/design-an-interface

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".

community

mattpocock/prototype

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.

community

mattpocock/grill-me

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".

community