quarkus-expert
quarkus-expert
Keyword: quarkus | Platforms: gemini,claude,codex
High-Performance Quarkus Framework Expert Skill - Deep production-grade knowledge of the Quarkus ecosystem.
Core Mandates
- Build-Time First: Move processing to augmentation phase, minimize runtime classpath scanning
- Java 21+ Excellence: Leverage Virtual Threads (
@RunOnVirtualThread) for blocking operations - Reactive Discipline: Use Mutiny (
Uni,Multi) for non-blocking I/O - Dependency Discipline: Always use Quarkus BOM for version management
- Constructor Injection: Mandate constructor injection over field injection
Architectural Patterns
Persistence Strategy
- Imperative: Hibernate ORM with Panache (Active Record or Repository pattern)
- Reactive: Reactive SQL Clients (MySQL, PostgreSQL, Oracle)
- Dev Services: Zero-config databases and brokers during development
Cloud-Native Observability
- OpenTelemetry (OTel): Standard for tracing and metrics
- Health Checks: Implement
LivenessandReadinessprobes using MicroProfile Health
Security Architecture
- Use Proactive Authentication and RBAC with
@RolesAllowed - Prefer OIDC/JWT for stateless microservices
Testing
- Integration Testing: Use
@QuarkusTestfor full-stack tests - Mocking: Utilize
@InjectMockand@InjectSpy - Parity: Use Testcontainers via Dev Services
Extension Development
- Build-Time (Deployment): Write
BuildStepmethods for bean registration, bytecode generation - Runtime Init: Differentiate between
STATIC_INITandRUNTIME_INIT
Troubleshooting
- ClassLoader Leaks: Monitor custom dynamic class loading
- ContextNotActiveException: Ensure CDI contexts propagate correctly with Mutiny
- Native Image Failures: Analyze reports and provide
reflection-config.json
🌐 Knowledge Sources & Deep Dives
Directive: Use
web_fetchto read specific guides if the user's question involves a particular extension (e.g., Hibernate, Kafka, OIDC).
- Mutiny Mastery: SmallRye Mutiny Documentation - Core reactive patterns.
- Persistence Guide: Hibernate ORM with Panache - Data access patterns.
- Messaging: Apache Kafka with Quarkus - Event-driven architecture.
- CDI/Arc: Contexts and Dependency Injection in Quarkus - Bean lifecycle and injection.
- Virtual Threads: Quarkus and Virtual Threads - Blocking I/O optimization.
References
Skill Interoperability
The quarkus-expert ⚡ skill is a comprehensive framework built on:
- java-expert ☕: Core language and JVM features.
- vertx-expert 🌀: Reactive engine for non-blocking operations.
- graalvm-expert 🚀: Native Image generation and AOT optimization.
More from kinhluan/rules-quarkus-skills
gradle-expert
Expert knowledge for Gradle Build Tool, dependency management, and Gradle-to-Bazel migration. Use for build configuration and project lifecycle questions.
15vertx-expert
Expert knowledge for Eclipse Vert.x, the reactive engine behind Quarkus. Use for deep reactive programming, Event Loop, and non-blocking I/O questions.
13bazel-expert
Expert knowledge for writing idiomatic Bazel rules, Starlark best practices, and build performance optimization. Use for Bazel build system questions.
9maven-expert
Expert knowledge for Apache Maven, dependency management, BOMs, and Maven-to-Bazel migration. Use for build configuration and project lifecycle questions.
9rules-quarkus
Expert knowledge for building Quarkus applications with Bazel using the rules_quarkus build system. Use when user asks about Quarkus+Bazel builds, augmentation, or troubleshooting.
8java-expert
Expert knowledge for Modern Java (21+) development, including Virtual Threads, performance tuning, and idiomatic clean code. Use for deep Java language/logic questions.
8