agentleFS
Sign inStart free
rrezartprebrezarrezartprebreza/spring-boot-skills/skills/spring-boot-3/spring-cloud-gateway/SKILL.md

spring-cloud-gateway

Skill344 starsChanged 3 months agoMITView on GitHub

Use when building or changing a Spring Cloud Gateway on Spring Boot 3. Covers route design, authentication, header hygiene, rate limiting, retries, timeouts, observability, and testing.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep the gateway an edge adapter.

    line 10
  2. Distinctive:

    Import the Spring Cloud BOM and omit individual Spring Cloud dependency versions.

    line 15
  3. Distinctive:

    Prefer the reactive gateway unless the project deliberately uses the MVC variant.

    line 16
  4. Distinctive:

    Use stable route IDs and explicit predicates.

    line 20
  5. Distinctive:

    Add correlation headers only after removing client-supplied values.

    line 22
  6. Distinctive:

    Keep path rewriting and host changes visible in route configuration.

    line 23
  7. Distinctive:

    Use circuit breakers for failing dependencies.

    line 32
  8. Distinctive:

    Test predicates, filters, header removal, status mapping, and timeouts.

    line 36
  9. Distinctive:

    Use WireMock or a containerized upstream for integration tests.

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Spring Cloud Gateway

Keep the gateway an edge adapter. Do not move domain workflows into filters.

Compatibility first

  • Select the Spring Cloud release train compatible with the exact Boot 3 minor.
  • Import the Spring Cloud BOM and omit individual Spring Cloud dependency versions.
  • Prefer the reactive gateway unless the project deliberately uses the MVC variant.

Route rules

  • Use stable route IDs and explicit predicates.
  • Strip untrusted forwarding, identity, and internal headers at the edge.
  • Add correlation headers only after removing client-supplied values.
  • Keep path rewriting and host changes visible in route configuration.
  • Set connect and response timeouts globally, with narrow route overrides.

Security and resilience

  • Authenticate at the edge and authorize again in downstream services.
  • Relay tokens only to intended audiences.
  • Rate-limit by trusted identity or API key, not an unverified header.
  • Retry only idempotent operations and only before response commitment.
  • Use circuit breakers for failing dependencies; never hide sustained failure with unlimited retries.

Testing and operations

  • Test predicates, filters, header removal, status mapping, and timeouts.
  • Use WireMock or a containerized upstream for integration tests.
  • Emit route ID, outcome, latency, and upstream metrics with bounded tags.

Examples

  • See examples/good-routes.yml and examples/bad-routes.yml.

Gotchas

  • Agent trusts X-User-Id from the public request - derive identity after authentication.
  • Agent retries POST requests by default - retry only operations proven idempotent.
  • Agent adds business orchestration to a gateway filter - keep domain logic downstream.
  • Agent omits response timeouts - stalled upstreams can exhaust gateway resources.
  • Agent mixes incompatible Spring Cloud and Boot versions - use the official compatibility matrix.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free