Agent skill

Inngest Nextjs Patterns

by pproenca in pproenca/dot-skills

Inngest event-driven functions in a Next.js (App Router) project — creating the client, the /api/inngest route handler, typed events with Zod schemas, durable event-triggered functions, scheduled…

MITAuto-check: notesBackend & APIs

Install Inngest Nextjs Patterns

skills CLI
$ npx skills add pproenca/dot-skills --skill inngest-nextjs-patterns -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install pproenca/dot-skills inngest-nextjs-patterns --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.experimental/inngest-nextjs-patterns .claude/skills/inngest-nextjs-patterns && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
inngest-nextjs-patterns
GitHub stars
214
Token cost
~1.4k tokens
SKILL.md length
554 words
Files
11 (incl. references, assets)
Skills in repo
182
Repo updated
First seen
Licence
MIT

At a glance

Inngest event-driven functions in a Next.js (App Router) project — creating the client, the /api/inngest route handler, typed events with Zod schemas, durable event-triggered functions, scheduled…

  • Works in 4 steps: First time in this codebase? Read… → Pick a template from the catalog below… → Render it by substituting the documented… → …
  • Scaffolding Inngest patterns — and even if the user just says add a background job
  • SKILL.md covers When to Apply, How to Use, Available Templates and Quick Reference, plus 3 more sections
  • Calls npx

What it does

Inngest Nextjs Patterns is an agent skill from pproenca/dot-skills. Inngest event-driven functions in a Next.js (App Router) project — creating the client, the /api/inngest route handler, typed events with Zod schemas, durable event-triggered functions, scheduled cron functions, or fan-out orchestrators. Trigger when scaffolding Inngest patterns — and even if the user just says "add a background job", "process this async", "schedule X every hour", or "send an event when Y happens" in a Next.js codebase. Also trigger when reviewing existing Inngest code to enforce event-naming…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including reference files and assets (for example `config.json`, `gotchas.md` and `metadata.json`).

It sits in Backend & APIs, covering Scheduled and recurring tasks, Event-driven systems and Background jobs. It works with Next.js and Zod. The repository describes itself as: A collection of AI agent skills following the Agent Skills open format. The licence is MIT.

When your agent uses it

  • Scaffolding Inngest patterns — and even if the user just says add a background job
  • Process this async
  • Schedule X every hour
  • Send an event when Y happens in a Next.js codebase

Example prompts

  • “add a background job”
  • “process this async”
  • “schedule X every hour”
  • “/inngest-nextjs-patterns”

Requirements

  • Node.js

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. First time in this codebase? Read references/conventions.md before writing anything. The conventions explain why event names take a…
  2. Pick a template from the catalog below based on what you're creating.
  3. Render it by substituting the documented parameters. Each template has a parameter table at the top of its file.
  4. Wire it up: new functions must be added to src/inngest/functions/index.ts (the registry the route handler reads). The conventions doc…

What it can do on your machine

Read from SKILL.md and the folder at commit cf93c57. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Inngest Nextjs Patterns loads about 1.4k tokens when it runs, and up to ~4.8k if it reads all its reference files. Until then it costs about 149 tokens; SKILL.md has 554 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~149
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:44
    /localhost:8288. Set `INNGEST_DEV=1` in `.env.local` to point the SDK at it.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from pproenca/dot-skills at commit cf93c57, republished under its MIT licence (© pproenca). 554 words, ~1,437 tokens.

Download SKILL.mdSave it as .claude/skills/inngest-nextjs-patterns/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
inngest-nextjs-patterns
description
Inngest event-driven functions in a Next.js (App Router) project — creating the client, the /api/inngest route handler, typed events with Zod schemas, durable event-triggered functions, scheduled cron functions, or fan-out orchestrators. Trigger when scaffolding Inngest patterns — and even if the user just says "add a background job", "process this async", "schedule X every hour", or "send an event when Y happens" in a Next.js codebase. Also trigger when reviewing existing Inngest code to enforce event-naming, function-id stability, and step-idempotency conventions.

Inngest + Next.js Patterns

Templates and conventions for building event-driven, durable background work on Inngest from a Next.js App Router project. The skill enforces the conventions Inngest's own docs use (decentralized eventType() schemas, kebab-case stable function IDs, idempotent steps) so that retries, replays, and concurrency controls actually do what they advertise.

When to Apply

Read this skill when you are:

  • Setting up Inngest in a Next.js app for the first time (client + route handler + first function)
  • Adding a new background job, webhook handler, or scheduled task to a Next.js app
  • Defining a new domain event that other functions will trigger on
  • Orchestrating multi-step work that must survive process restarts (durable workflows, sagas)
  • Reviewing existing Inngest code for event naming, step idempotency, or stable function IDs
  • Migrating from setTimeout / a queue library / a cron service to Inngest's durable execution model

How to Use

  1. First time in this codebase? Read references/conventions.md before writing anything. The conventions explain why event names take a specific shape, why function IDs must be stable, and why every step.run must be idempotent — once you understand the reasoning, the templates make sense.
  2. Pick a template from the catalog below based on what you're creating.
  3. Render it by substituting the documented parameters. Each template has a parameter table at the top of its file.
  4. Wire it up: new functions must be added to src/inngest/functions/index.ts (the registry the route handler reads). The conventions doc shows the registry pattern.

Available Templates

TemplateOutput PathUse When
client.ts.templatesrc/inngest/client.tsOne-time setup: create the singleton Inngest client. Generate once per app.
route-handler.ts.templatesrc/app/api/inngest/route.tsOne-time setup: the App Router endpoint Inngest hits to invoke your functions. Generate once per app.
event.ts.templatesrc/inngest/events/{domain}.tsDefining a new typed event (with Zod schema) that producers send and functions consume.
function.ts.templatesrc/inngest/functions/{name}.tsStandard event-triggered durable function with steps. Parameterized retries, concurrency, throttle, debounce, cancelOn, onFailure.
function-cron.ts.templatesrc/inngest/functions/{name}.tsScheduled function — runs on a cron expression (with timezone). Optionally also accepts a manual event trigger for ad-hoc invocation.
function-fan-out.ts.templatesrc/inngest/functions/{name}.tsOrchestrator that receives one event and fans out work — via step.sendEvent (fire-and-forget) or Promise.all(step.invoke(...)) (wait for results).
Show full SKILL.md (204 more words)Show less

Quick Reference

  • Event name shape: domain/entity.verb_past — e.g., app/user.created, shop/order.placed, billing/invoice.paid. The conventions doc has the full rule.
  • Function id: stable kebab-case, never rename it after deploy — Inngest uses it as the durable state key.
  • Step id: descriptive kebab-case, also durable; changing one re-runs that step on replay.
  • Idempotency: every step.run must be safely retryable. If it calls a third-party API that mutates state, pass an idempotency key.
  • Dev server: npx inngest-cli@latest dev, then UI at http://localhost:8288. Set INNGEST_DEV=1 in .env.local to point the SDK at it.

Project Layout Assumption

Templates assume a src/ directory with App Router:

src/
├── app/api/inngest/route.ts          # generated by route-handler template
└── inngest/
    ├── client.ts                     # generated by client template
    ├── events/                       # one file per domain (events.shop.ts, events.user.ts)
    │   └── {domain}.ts               # generated by event template
    └── functions/
        ├── index.ts                  # registry: re-exports all functions as an array
        └── {name}.ts                 # generated by function/cron/fan-out templates

If your project uses a different layout (no src/, or Pages Router), override the output paths in config.json. The conventions doc explains the trade-offs.

Setup

config.json controls path overrides. On first use, check whether its fields are filled in — if not, ask the user before generating (project root differs from the default assumption).

  • vercel:ai-sdk — if your Inngest functions invoke LLMs, the AI SDK gives you streaming + provider abstraction; pair them with step.run for retry safety.
  • vercel:vercel-functions — Inngest's serve() adapter for Next.js runs as a Vercel Serverless Function by default; the AI SDK skill has notes on Fluid Compute and timeout extension for long agent runs.

© pproenca, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 10 other files (references, assets) in skills/.experimental/inngest-nextjs-patterns of pproenca/dot-skills.

  • SKILL.md
  • assets/templates/client.ts.template
  • assets/templates/event.ts.template
  • assets/templates/function-cron.ts.template
  • assets/templates/function-fan-out.ts.template
  • assets/templates/function.ts.template
  • assets/templates/route-handler.ts.template
  • config.json
  • gotchas.md
  • metadata.json
  • references/conventions.md

Open the folder on GitHubat commit cf93c57

Compare with similar skills

Inngest Nextjs Patterns next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Inngest Nextjs Patterns compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Inngest Nextjs Patterns this skillpproenca/dot-skills214—~1.4kAutomated safety check: NotesMIT
Trigger.dev Background Taskspapermark/papermark9.2k—~2.1kAutomated safety check: PassCustom licence
Backend Dev Guidelineslitefuse/litefuse1001 repos~5.8kAutomated safety check: PassCustom licence
Inngestpedronauck/skills6334 repos~3.1kAutomated safety check: PassNone
Upstash Qstashdavila7/claude-code-templates32k4 repos~597Automated safety check: PassMIT
Nextjs SecurityHoangNguyen0403/agent-skills-standard570—~688Automated safety check: PassMIT

Similar skills

  • Trigger.dev Background Tasks

    papermark/papermark

    Guides building durable background tasks, scheduled jobs and queues with Trigger.dev, including retries, waits, idempotency and concurrency limits.

    9.2k GitHub stars~2.1k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed
  • Backend Dev Guidelines

    litefuse/litefuse

    Comprehensive backend development guide for Litefuse's Next.js 14/tRPC/Express/TypeScript monorepo.

    100 GitHub starsUsed in 1 repo~5.8k tokens
    Backend & APIsAuto-check passed
  • Inngest

    pedronauck/skills

    Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers.

    633 GitHub starsUsed in 4 repos~3.1k tokens
    Backend & APIsAuto-check passed
  • Upstash Qstash

    davila7/claude-code-templates

    Upstash QStash expert for serverless message queues, scheduled jobs, and reliable HTTP-based task delivery without managing infrastructure.

    32k GitHub starsUsed in 4 repos~597 tokens
    Backend & APIsAuto-check passed
  • Nextjs Security

    HoangNguyen0403/agent-skills-standard

    Secure Next.js App Router with middleware auth, Server Action validation, CSP headers, and taint APIs.

    570 GitHub stars~688 tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Inngest Setup

    Asymmetric-al/core

    A skill your agent uses when adding durable execution to a TypeScript project — building retry-safe webhook handlers, background jobs that survive crashes, scheduled tasks, or long-running workflows…

    382 GitHub stars~3.3k tokensUpdated today
    Backend & APIsAuto-check: notes

More from pproenca/dot-skills

All 182 skills in this repo
  • Audio Voice Recovery

    pproenca/dot-skills

    Audio forensics and voice recovery guidelines for CSI-level audio analysis.

    214 GitHub stars~3.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Codemod React Pipeline

    pproenca/dot-skills

    Guided, scripted pipeline for running JSX/TSX/React codemods safely across large legacy codebases.

    214 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed
  • Dev Rfc

    pproenca/dot-skills

    Create well-structured RFCs and technical proposals for software projects.

    214 GitHub stars~3.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Dx Harness

    pproenca/dot-skills

    Developer-experience friction auditing and fixing — slow onboarding, repeated manual setup steps, missing bootstrap/reset/seed scripts, undiscoverable conventions.

    214 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed
  • Language Spec Author

    pproenca/dot-skills

    Turn a rough idea for a language into a complete, implementable specification — a DSL, query, config/data, template, or protocol language — by interviewing the author dimension by dimension until…

    214 GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed
  • Python Pep Author

    pproenca/dot-skills

    Drafting Python Enhancement Proposals (PEPs) — proposing a Python language feature, a standard library change, an interoperability standard, or an informational/process document for the Python…

    214 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Inngest Nextjs Patterns

What does Inngest Nextjs Patterns do?

Inngest event-driven functions in a Next.js (App Router) project — creating the client, the /api/inngest route handler, typed events with Zod schemas, durable event-triggered functions, scheduled…. Inngest Nextjs Patterns is an agent skill from pproenca/dot-skills.js (App Router) project — creating the client, the /api/inngest route handler, typed events with Zod schemas, durable event-triggered functions, scheduled cron functions, or fan-out orchestrators.

When should I use Inngest Nextjs Patterns?

Inngest Nextjs Patterns fits situations like: scaffolding Inngest patterns — and even if the user just says add a background job; process this async; schedule X every hour; send an event when Y happens in a Next.js codebase.

How do I install Inngest Nextjs Patterns in Claude Code?

Run `npx skills add pproenca/dot-skills --skill inngest-nextjs-patterns -a claude-code`. Or copy the skill folder (skills/.experimental/inngest-nextjs-patterns in pproenca/dot-skills) into .claude/skills/inngest-nextjs-patterns in your project. Claude Code loads it when a task matches its description.

How do I install Inngest Nextjs Patterns in Codex?

Run `npx skills add pproenca/dot-skills --skill inngest-nextjs-patterns -a codex`. Or copy the skill folder (skills/.experimental/inngest-nextjs-patterns in pproenca/dot-skills) into .agents/skills/inngest-nextjs-patterns in your project. Codex loads it when a task matches its description.

Can I use Inngest Nextjs Patterns in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pproenca/dot-skills --skill inngest-nextjs-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/inngest-nextjs-patterns, .gemini/skills/inngest-nextjs-patterns, .github/skills/inngest-nextjs-patterns and .opencode/skills/inngest-nextjs-patterns in your project.

What does Inngest Nextjs Patterns need to run?

Going by SKILL.md and its folder, Inngest Nextjs Patterns needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Inngest Nextjs Patterns access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Inngest Nextjs Patterns safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Inngest Nextjs Patterns use?

Inngest Nextjs Patterns is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Inngest Nextjs Patterns use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.4k tokens, read only when the agent opens those files.

What are the alternatives to Inngest Nextjs Patterns?

Skills that share tags, products or a category with Inngest Nextjs Patterns: Trigger.dev Background Tasks (papermark/papermark, 9.2k stars), Backend Dev Guidelines (litefuse/litefuse, 100 stars), Inngest (pedronauck/skills, 633 stars) and Upstash Qstash (davila7/claude-code-templates, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Inngest Nextjs Patterns?

pproenca (a GitHub user) maintains it in pproenca/dot-skills, which has 214 GitHub stars. The repository holds 182 skills in this directory. The repository was last updated on August 15, 2026.

Source: pproenca/dot-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.