dcyfr-api-patterns

Enforce a Validate → Queue → Respond workflow with Inngest for API routes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dcyfr/dcyfr-labs --skill dcyfr-api-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dcyfr-api-patterns
Source: https://github.com/dcyfr/dcyfr-labs/tree/main/.opencode/skill/dcyfr-api-patterns
Command: npx skills add https://github.com/dcyfr/dcyfr-labs --skill dcyfr-api-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce a consistent API route pattern by applying the Validate → Queue → Respond flow with Inngest, delivering reliable, non-blocking user experiences.

Core Features & Use Cases

  • Enforces Validate → Queue → Respond pattern for API routes.
  • Integrates Inngest for background processing and event-driven workflows.
  • Provides standardized error handling and rate limiting for robust APIs.
  • Suitable for creating new API endpoints, form submissions, and webhooks requiring asynchronous processing.

Quick Start

Create a new API route that validates input, queues work via Inngest, and responds immediately with a 202 Accepted.

Frequently Asked Questions about dcyfr-api-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize API routes for asynchronous processing in TypeScript?

Standardize API routes by enforcing a Validate → Queue → Respond workflow with Inngest. This pattern validates input, offloads heavy work to background processes, and returns non-blocking responses with standardized error handling and rate limiting.

What is the best way to handle webhooks without blocking the response?

Handling webhooks without blocking requires queuing work via Inngest after validating input. The API route responds immediately with a 202 Accepted, offloading the actual webhook processing to an asynchronous background event.

How do I implement rate limiting and error handling for API endpoints consistently?

Implement consistent rate limiting and error handling by applying a standardized API route pattern. This approach validates requests, queues tasks via Inngest, and ensures robust, non-blocking responses across new endpoints and form submissions.

Can I use this Validate Queue Respond pattern for form submissions?

Yes, the Validate → Queue → Respond pattern suits form submissions perfectly. It validates the submission input, queues the processing task in Inngest, and responds immediately, delivering a reliable non-blocking user experience.

When should I offload API work to a background queue instead of processing synchronously?

Offload API work to a background queue when handling long-running tasks like webhooks or form submissions. The Validate → Queue → Respond pattern with Inngest ensures the API remains responsive by returning a 202 Accepted immediately.