api-gateway-design

Design API gateways with routing, authentication, and rate limiting.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/Prathmesh2000/cursor_agent-orchestrator --skill api-gateway-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-gateway-design
Source: https://github.com/Prathmesh2000/cursor_agent-orchestrator/tree/main/agent-system/skills/api-gateway-design
Command: npx skills add https://github.com/Prathmesh2000/cursor_agent-orchestrator --skill api-gateway-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

API gateway design consolidates exposure of multiple microservices behind a single entry point, providing consistent routing, security, and observability to reduce integration complexity and runtime costs.

Core Features & Use Cases

  • Routing and request aggregation to minimize client round-trips.
  • Security and resilience through JWT-forwarding, rate limiting, and circuit breakers.
  • Observability and governance with correlation IDs, logging, and versioned APIs.
  • Use Case: When you have multiple services (users, orders, catalog) you deploy a gateway to present a unified API surface and enforce cross-cutting policies.

Quick Start

Install and run a lightweight Express gateway and wire up downstream services, then configure authentication, rate limits, and proxies to expose a single entry point.

Frequently Asked Questions about api-gateway-design

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

FAQPage Schema
What is an API gateway in microservices and when do I need one?

An API gateway provides a unified entry point for multiple microservices, consolidating routing, security, and observability. You need an API gateway when exposing multiple services like users, orders, or catalog to enforce cross-cutting policies and reduce integration complexity.

How do I implement JWT validation and forwarding in an API gateway?

You can implement JWT validation forwarding at the API gateway level to authenticate requests before routing them downstream. This centralizes security by validating tokens at the gateway and forwarding authenticated requests to microservices.

How does request aggregation in an API gateway reduce client round-trips?

Request aggregation in an API gateway combines multiple downstream microservice calls into a single response. By routing and aggregating requests at the gateway, you minimize client round-trips and reduce runtime costs for frontend applications.

Can I use the Backend for Frontend (BFF) pattern with a microservices API gateway?

Yes, the API gateway supports the Backend for Frontend (BFF) pattern to provide tailored API surfaces for different clients. This pattern works with routing and request aggregation to minimize client round-trips and optimize frontend integration.

How do I add observability and correlation IDs to a microservices gateway?

You add gateway-level observability by propagating correlation IDs across routed requests and centralizing logging. This ensures distributed requests across multiple microservices are traceable, making the gateway secure, scalable, and observable.

What is the best way to handle circuit breaking and rate limiting in an API gateway?

The best way to handle resilience is configuring circuit breakers and rate limits directly at the API gateway. This protects downstream microservices from cascading failures and excessive load by enforcing centralized security and traffic control policies.