Configure API gateways for routing, authentication, rate limiting, and request/response transformation. Use when deploying microservices, setting up reverse proxies, or managing API traffic.
Design and configure API gateways to handle routing, authentication, rate limiting, and request/response transformation for microservice architectures.
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)
Detailed implementations in the references/ directory:
| Guide | Contents | |---|---| | Kong Configuration | Kong Configuration | | Nginx Configuration | Nginx Configuration | | AWS API Gateway Configuration | AWS API Gateway Configuration | | Traefik Configuration | Traefik Configuration | | Node.js Gateway Implementation | Node.js Gateway Implementation |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/api-gateway-configuration · pinned to the source commit
git clone https://github.com/aj-geddes/useful-ai-prompts.git
cd useful-ai-prompts
git checkout 3f5182cfd739fc113f4af5244a1cf342ad7f7911
mkdir -p ".claude/skills/api-gateway-configuration"
cp -r "skills/api-gateway-configuration" ".claude/skills/api-gateway-configuration"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 3f5182cfd739. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
References credentials, tokens or secret files that a skill should not need.
Evidence: [redacted]· fingerprint 85dbe15d75ef9308