Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aj-geddes avatar

Api Gateway Configuration

  • 454 installs
  • 305 repo stars
  • Updated March 4, 2026
  • aj-geddes/useful-ai-prompts

api-gateway-configuration is an agent skill that configures API gateways with routes, JWT auth, rate limits, CORS, and upstream routing for developers deploying microservices or public API edges.

About

api-gateway-configuration is a prompt skill in aj-geddes/useful-ai-prompts for designing API gateway layers that centralize authentication, rate limiting, routing, and request transformation. The quick-start Kong YAML example defines a user-service upstream, /api/users routes, rate-limiting at 100 requests per minute, JWT validation, and CORS origins. Five reference guides cover Kong, Nginx, AWS API Gateway, Traefik, and Node.js gateway implementations with production-focused patterns. Best practices urge gateway-level auth, global rate limits, backend health checks, response caching where safe, circuit breakers, HTTPS enforcement, and comprehensive access logging while warning against exposing internal IPs or skipping validation. Developers reach for this skill when standing up reverse proxies for microservices, enforcing quotas, or versioning public APIs behind a single edge. Use it during architecture passes where TLS termination, plugin configuration, and upstream timeouts must be decided before services go live.

  • route mapping
  • rate limiting
  • auth plugins
  • TLS setup
  • upstream routing

Api Gateway Configuration by the numbers

  • 454 all-time installs (skills.sh)
  • Ranked #373 of 1,039 Cloud & Infrastructure skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill api-gateway-configuration

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs454
repo stars305
Last updatedMarch 4, 2026
Repositoryaj-geddes/useful-ai-prompts

How do you configure an API gateway for microservices?

Configure API gateways with route maps, rate limits, auth plugins, TLS termination, CORS rules, and upstream routing for microservices or public APIs.

Who is it for?

Platform developers centralizing microservice traffic who need gateway YAML for Kong, Nginx, AWS API Gateway, or Traefik with auth and quotas.

Skip if: Application teams with a single monolith and no edge gateway requirement should skip api-gateway-configuration.

When should I use this skill?

User sets up reverse proxies, central API auth, rate limiting, or routes microservices through Kong, Traefik, or AWS API Gateway.

What you get

Gateway route maps, auth and rate-limit plugin configs, TLS termination settings, and upstream health-checked service definitions.

  • Gateway YAML or config files
  • Route and plugin definitions
  • Auth and rate-limit policies

By the numbers

  • Documents 5 gateway reference guides in references/
  • Kong sample rate-limiting plugin configured at 100 requests per minute

Files

SKILL.mdMarkdownGitHub ↗

API Gateway Configuration

Table of Contents

Overview

Design and configure API gateways to handle routing, authentication, rate limiting, and request/response transformation for microservice architectures.

When to Use

  • Setting up reverse proxies for microservices
  • Centralizing API authentication
  • Implementing request/response transformation
  • Managing traffic across backend services
  • Rate limiting and quota enforcement
  • API versioning and routing

Quick Start

Minimal working example:

# kong.yml - Kong Gateway configuration
_format_version: "2.1"
_transform: true

services:
  - name: user-service
    url: http://user-service:3000
    routes:
      - name: user-routes
        paths:
          - /api/users
          - /api/profile
    plugins:
      - name: rate-limiting
        config:
          minute: 100
          policy: local
      - name: jwt
        config:
          secret: your-secret-key
          key_claim_name: "sub"
      - name: cors
        config:
          origins:
            - "http://localhost:3000"
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
Kong ConfigurationKong Configuration
Nginx ConfigurationNginx Configuration
AWS API Gateway ConfigurationAWS API Gateway Configuration
Traefik ConfigurationTraefik Configuration
Node.js Gateway ImplementationNode.js Gateway Implementation

Best Practices

✅ DO

  • Centralize authentication at gateway level
  • Implement rate limiting globally
  • Add comprehensive logging
  • Use health checks for backends
  • Cache responses when appropriate
  • Implement circuit breakers
  • Monitor gateway metrics
  • Use HTTPS in production

❌ DON'T

  • Expose backend service details
  • Skip request validation
  • Forget to log API usage
  • Use weak authentication
  • Over-cache dynamic data
  • Ignore backend timeouts
  • Skip security headers
  • Expose internal IPs

Related skills

How it compares

Pick api-gateway-configuration over api-error-handling when the task is edge routing, auth plugins, and quotas rather than in-service error JSON design.

FAQ

Which gateways does api-gateway-configuration cover?

api-gateway-configuration includes 5 reference implementations for Kong, Nginx, AWS API Gateway, Traefik, and a Node.js gateway, each documenting routes, plugins, auth, and upstream patterns.

What does the Kong quick start configure?

The api-gateway-configuration Kong example defines a user-service upstream, /api/users routes, rate-limiting at 100 requests per minute, JWT secret validation, and CORS origins for localhost development.

Cloud & Infrastructurebackendintegrationsdevops

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.