Back to Skills

quarkus-patterns

Quarkus 3.x LTS architecture patterns with Camel for messaging, RESTful API design, CDI services, data access with Panache, and async processing. Use for Java Quarkus backend work with event-driven architectures.

232,591stars35,447forksUpdated 7/24/2026

Security Assessment

Safe(96/100)
Security Score96/100

About quarkus-patterns

quarkus-patterns is a reference/guidance skill documenting architecture and API patterns for building cloud-native, event-driven backend services with Quarkus 3.x LTS and Apache Camel. It solves the problem of inconsistent structure in Java backends by codifying conventions for layering, messaging, data access, logging, and async processing that an agent can apply when writing or reviewing Quarkus code.

The SKILL.md specifies when to activate (JAX-RS/RESTEasy Reactive APIs, resource-service-repository layering, Camel and RabbitMQ event-driven flows, Hibernate Panache, validation and exception mapping, environment profiles, GraalVM native compilation) and provides annotated Java examples. These include a service layer using constructor injection and @Transactional, a success/error event service with payload serialization, an MDC-style Logback logging-context pattern with a Logstash encoder, Camel routes for RabbitMQ publishing and in-memory direct routes, and error handling via onException. The patterns emphasize validating input before persistence or message publication and tracking success and error events.

It targets Java backend engineers working on Quarkus microservices with event-driven, message-based architectures. Typical uses include scaffolding REST resources and services, wiring Camel messaging, standardizing structured logging, and reviewing code for adherence to these conventions. It is documentation and example code only, with no destructive or network-exfiltration behavior; RabbitMQ hosts and queues are read from configuration properties.

FAQ

What versions and frameworks does it target?

Quarkus 3.x LTS with Apache Camel for messaging, RESTEasy Reactive/JAX-RS for APIs, Hibernate Panache for data access, and RabbitMQ as the message broker.

What patterns are included?

Service layering with constructor injection and @Transactional, a success/error event service, an MDC-style Logback logging context with a Logstash encoder, Camel RabbitMQ and in-memory direct routes, and Camel exception handling.

Does it run commands or modify infrastructure?

No. It is a documentation skill with annotated Java and XML examples; it provides patterns to apply, not scripts that execute against a live system.

How are broker connection details handled?

The Camel route examples read RabbitMQ host, port, and queue name from @ConfigProperty configuration values rather than hardcoding them, so credentials/connection settings come from your environment.

Who is it for?

Java backend developers building or reviewing event-driven Quarkus microservices who want consistent, idiomatic architecture patterns.

Install quarkus-patterns

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill