What is the Epic architecture pattern for integrations?

The Epic architecture places integrations in the Infrastructure layer. They handle external API calls and complex logic and are called exclusively by the Backend layer (Actions and Routes).

How does this skill handle sensitive API keys?

It generates code that uses environment variables for all secrets and includes 'server-only' imports to ensure sensitive logic never reaches the client-side bundle.

Does the generated code include error handling?

Yes, it implements a standard pattern including try/catch blocks, rate-limit handling, and configurable retry logic for transient network failures.

Can I use this for custom internal APIs?

Absolutely. While it has presets for common services like Stripe or OpenAI, the pattern is designed to work with any external REST, GraphQL, or SDK-based service.

Epic Service Integrator

Name: Epic Service Integrator
Author: coeus-ventures

bycoeus-ventures

API Development

Builds standardized, production-grade external API integrations and business logic services using the Epic three-layer architecture pattern.

About

This skill streamlines the creation of external service integrations within the Epic architecture, ensuring consistency and reliability across your backend. It automates the generation of Infrastructure-layer classes for third-party APIs like Stripe, OpenAI, or Twilio, enforcing strict server-only boundaries, standardized error handling, and built-in retry logic. By following these predefined patterns, developers can quickly implement robust services for payments, communications, and cloud storage while maintaining a clean separation from frontend components and application routes.

Key Features

Generates class-based service integrations following the Epic three-layer architecture.
Provides built-in templates for retry logic and transient failure handling.
Implements standardized success/error return types for predictable service responses.
Supports specific patterns for Payments, AI, Communication, and Storage providers.
0 GitHub stars
Enforces 'server-only' constraints to prevent sensitive code from leaking to the frontend.

Use Cases

Setting up transactional email or SMS services with providers like Resend or Twilio.
Integrating AI capabilities from providers like Anthropic or OpenAI into server-side logic.
Connecting to payment gateways like Stripe for secure checkout and webhook management.

About

Key Features

Generates class-based service integrations following the Epic three-layer architecture.
Provides built-in templates for retry logic and transient failure handling.
Implements standardized success/error return types for predictable service responses.
Supports specific patterns for Payments, AI, Communication, and Storage providers.
0 GitHub stars
Enforces 'server-only' constraints to prevent sensitive code from leaking to the frontend.

Use Cases

Setting up transactional email or SMS services with providers like Resend or Twilio.
Integrating AI capabilities from providers like Anthropic or OpenAI into server-side logic.
Connecting to payment gateways like Stripe for secure checkout and webhook management.