kong Architecture Review Prompt

architecturevery high Token Costadvanced

Prompt provenance

Inspired by Kong/kong.

Reverse-engineered from real GitHub workflow.

Updated 2 weeks ago·0 copies

Review an API gateway repository by tracing runtime startup, route and service matching, plugin phase execution, upstream proxying, Admin API mutation paths, control-plane sync, observability, AI gateway plugins, and production failure modes.

What this solves

API gateway architecture and operational boundary review

Best used when

You need to understand how a gateway accepts a request, matches a route, runs plugins, proxies upstream, and records latency or failure signals.
You are reviewing API gateway boundaries around routes, services, consumers, plugins, auth, Admin API writes, control-plane/data-plane sync, or AI gateway extensions.
You want a source-grounded checklist before changing gateway routing, plugin execution, observability, or production operations.

Avoid using when

You only need a quick Kong installation guide or plugin usage snippet.
You are reviewing a small reverse proxy with no route table, plugin model, Admin API, or control-plane/data-plane split.
You want to publish production prompt rows directly without maintainer review.

Prompt Variants

Use this when Claude has broad repo-reading access and should produce a structured, source-cited architecture review of an API gateway, plugin system, and control-plane/data-plane workflow.