Vertx expert
Skill kinhluan/rules-quarkus-skills/.agent-skills/vertx-expert
π€ Complete AI expert ecosystem for Modern Java, Quarkus & Bazel development βοΈβ‘οΈ Coverage for Vert.x, GraalVM, Maven/Gradle migration, and more π
npx -y skills add kinhluan/rules-quarkus-skills --skill vertx-expertAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Expert knowledge for Eclipse Vert.x, the reactive engine behind Quarkus. Use for deep reactive programming, Event Loop, and non-blocking I/O questions.
SKILL.md
3.2 KB, as published. Nobody here has run it
vertx-expert
Keyword: vertx | Platforms: gemini,claude,codex
Reactive Foundation Expert Skill - Specialized in the Eclipse Vert.x event-driven ecosystem.
Core Mandates
- Don't Block the Event Loop: Never perform blocking operations (I/O, heavy computation) in an Event Loop thread. Use
executeBlocking()if needed. - Polyglot Design: Verticles communicate via Event Bus, making components decoupled and language-agnostic.
- Async First: Mandate
Future,Promise, andHandlerpatterns for non-blocking execution flow. - Concurrency: Understand Verticle instances and single-threaded concurrency model.
Reactive Vert.x Components
- Vert.x Web: Building high-performance, non-blocking HTTP APIs.
- Event Bus: Distributed messaging system for horizontal scaling.
- Reactive Clients: Using MySQL, PostgreSQL, Redis, and Kafka clients without blocking threads.
- Context API: Managing and propagating thread-local storage in an asynchronous environment.
Vert.x + Quarkus Integration
- Reactive Engine: Understanding how Quarkus uses Vert.x as its underlying I/O engine.
- Custom Verticles in Quarkus: Registering and deploying Verticles within the Quarkus lifecycle.
- Vert.x Mutiny: Leveraging SmallRye Mutiny (
Uni,Multi) over standard Vert.x Futures.
Advanced Patterns
- Circuit Breaker: Handling service failures gracefully in a distributed system.
- Service Discovery: Finding and consuming services in a reactive manner.
- Clustering: Using Hazelcast or Infinispan to cluster the Event Bus.
Expert Tips
- Monitor the Event Loop using
BlockedThreadCheckerlog warnings. - Prefer
Vert.x Web Clientover legacyRestTemplateor blocking clients. - Use
Vertx.currentContext()for low-level async state management.
π Reactive Knowledge Sources
Directive: If you encounter blocked thread warnings or need to implement complex event-driven flows, use
web_fetchon these official guides.
- Don't Block!: Blocking Code in Vert.x Guide - Essential reading for performance.
- Event Bus Patterns: Vert.x Distributed Event Bus - Messaging and scaling.
- Reactive SQL: Vert.x Reactive SQL Clients - Non-blocking database access.
- Vert.x + Mutiny: SmallRye Mutiny for Vert.x - Reactive patterns for Quarkus.
References
Skill Interoperability
The vertx-expert π skill serves as the reactive engine for:
- quarkus-expert β‘: Quarkus is built on top of Vert.x for non-blocking I/O and high performance. It depends on java-expert β for language-level reactive features.