Skip to content

rrezartprebreza/spring-boot-skills / skills/spring-boot-4/webflux-reactive-patterns

webflux-reactive-patterns

Verified

Use when the complete Spring Boot 4 request path is reactive: WebFlux controllers, Reactor pipelines, R2DBC persistence, streaming, backpressure, or cancellation. For defining and registering declarative outbound API interfaces, use http-interface-clients.

WebFlux Reactive Patterns

Use WebFlux when the complete request path benefits from non-blocking I/O.

Dependencies and pipeline rules

  • Use the dedicated Boot 4 WebFlux and WebFlux test starters.
  • Return Mono or Flux; never call subscribe() in request-handling code.
  • Choose flatMap, concatMap, or sequential composition according to ordering needs.
  • Keep JDBC, filesystem, and blocking SDK calls off Reactor event loops.
  • Isolate unavoidable blocking work on boundedElastic at the adapter boundary.
  • Apply timeouts to external calls and preserve cancellation.

Context and errors

  • Put request-scoped metadata in Reactor Context, not ThreadLocal.
  • Configure observability context propagation deliberately.
  • Translate domain failures centrally without swallowing cancellation.
  • Use onErrorResume only for a defined fallback and avoid onErrorContinue.

Persistence and streaming

  • Use R2DBC for reactive database access.
  • Bound fan-out concurrency according to downstream capacity.
  • Define backpressure, buffering, and maximum in-memory sizes.
  • Never collect an unbounded stream solely to simplify downstream code.

Testing

  • Use StepVerifier for publisher behavior and WebTestClient for contracts.
  • Test cancellation, timeout, empty results, errors, ordering, and backpressure.
  • Detect blocking calls in tests when practical.

Examples

  • See examples/good-reactive-service.java and examples/bad-reactive-service.java.

Official sources

Verification scope

The workflow fixture compiles good-reactive-service.java directly and checks found/missing results, upstream errors, virtual-time timeout and cancellation propagation. It does not verify a WebFlux HTTP server, R2DBC driver or reactive tenant context. See the coverage matrix for pinned versions and remaining gaps.

Gotchas

  • Agent adds MVC and WebFlux starters accidentally - choose the intended web stack.
  • Agent calls block() or subscribe() in application flow - keep subscription with the runtime.
  • Agent uses ThreadLocal for tenant or trace data - use Reactor Context.
  • Agent uses unbounded flatMap - set concurrency from downstream limits.
  • Agent wraps JDBC with Mono.just - this still blocks the event loop.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall