Communitygithub.com

inngest/inngest-events

Use ao projetar fluxos de trabalho orientados a eventos, desacoplar serviços, implementar padrões fan-out (um gatilho, vários manipuladores downstream), lidar com eventos idempotentes com IDs (janela de deduplicação de 24 horas) ou processar entrega pelo menos uma vez de fontes externas como webhooks do Stripe. Abrange o schema de eventos do Inngest, formato de payload, convenções de nomenclatura, IDs para idempotência, o parâmetro ts, padrões fan-out e eventos de sistema como inngest/function.failed.

O que é inngest-events?

Esta skill fornece um guia abrangente sobre o sistema de eventos do Inngest, essencial para arquitetar fluxos de trabalho orientados a eventos de forma confiável. Ela detalha o formato do payload do evento, as convenções de nomenclatura e o uso de IDs de idempotência para garantir que eventos sejam processados exatamente uma vez dentro de uma janela de 24 horas, prevenindo duplicatas. A skill também cobre padrões de fan-out, que permitem que um único evento gatilhe múltiplas funções handler simultaneamente, e explica como lidar com eventos de sistema como `inngest/function.failed` para tratamento de erros. Útil para engenheiros de software que trabalham com o Inngest em qualquer plataforma suportada (Cloud, Dev Server, Open Source), ajuda a implementar serviços desacoplados e processar entregas pelo menos uma vez de fontes externas, como webhooks do Stripe, com confiança.

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

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

Documentação

O que inngest-events faz?

Use ao projetar fluxos de trabalho orientados a eventos, desacoplar serviços, implementar padrões fan-out (um gatilho, vários manipuladores downstream), lidar com eventos idempotentes com IDs (janela de deduplicação de 24 horas) ou processar entrega pelo menos uma vez de fontes externas como webhooks do Stripe. Abrange o schema de eventos do Inngest, formato de payload, convenções de nomenclatura, IDs para idempotência, o parâmetro ts, padrões fan-out e eventos de 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.

Habilidades Relacionadas

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