Skip to content

Guide · Agent skill

How to use the Quarkus Patterns agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The quarkus-patterns skill is a set of reference patterns that tells an AI agent how to write Java back-end services with Quarkus 3.x, including Apache Camel messaging with RabbitMQ and Hibernate Panache data access. It is written for Java developers building cloud-native or event-driven services. After this guide you will know what the skill changes about the agent's output, how to install it, how to trigger it, and what to check before using the generated code.

Quarkus Patternsaffaan-m/ECC · MIT

Quick start

  1. 1Download the ZIP. Download the quarkus-patterns ZIP from this page.
  2. 2Unzip the skill. Unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder.
  3. 3Or upload it in the Claude apps. Go to Settings → Capabilities → Skills and upload the skill there.
  4. 4Describe your Quarkus task. Ask for the Quarkus work in plain language and name the technology, such as Panache or RabbitMQ.
  5. 5Review the output. Check imports, dependencies, configuration keys and transaction boundaries against your project.
  6. 6Test before deploying. Run the code against your own dependencies and, for messaging, a RabbitMQ broker.

What does the quarkus-patterns skill make the agent do?

An agent skill is a folder with a SKILL.md file that an AI agent reads when it is relevant to your request. This skill gives the agent documented Quarkus conventions: a layered style of resource, service and repository, constructor injection with Lombok, transactions around write operations, and event-driven messaging with Apache Camel and RabbitMQ.

It is a set of coding conventions and code examples, not a program you run. It does not add tools or change your project on its own; it only shapes how the agent writes Quarkus code when you ask for it.

  • Builds REST APIs with JAX-RS or RESTEasy Reactive
  • Structures code as resource, service and repository layers
  • Uses @RequiredArgsConstructor for constructor injection and @Slf4j for logging
  • Marks service methods that write through Panache or repositories with @Transactional
  • Shows Camel routes that publish to RabbitMQ and handle file processing
  • Covers logging context with Logback and the Logstash encoder, profiles, validation, pagination and GraalVM native builds

How do you install the quarkus-patterns skill?

Download the ZIP from this page and unzip it. You can install the skill in one of two ways: put the folder in your personal skills directory, or in a single project's skills directory. Either way, the folder must contain SKILL.md.

To use it in the Claude apps, upload the skill under Settings → Capabilities → Skills instead.

  • Personal install: unzip into ~/.claude/skills/
  • Project install: unzip into the project's .claude/skills/ folder
  • Claude apps: Settings → Capabilities → Skills, then upload the skill

How do you trigger the skill with a natural request?

You do not need a special command. Describe the Quarkus work you want in plain language and mention the relevant technology. The skill is designed to activate for topics such as REST APIs, layered services, Camel and RabbitMQ messaging, Hibernate Panache, CompletableFuture, GraalVM and logging with Logback.

Be specific about your stack. A request that names Quarkus, Panache or RabbitMQ gives the agent clearer signals than a generic request about Java.

  • "Create a Quarkus REST resource and service for orders, following a resource, service and repository layout."
  • "Add a Camel route that publishes order events to RabbitMQ from my Quarkus service."
  • "Write a Panache repository and a @Transactional service method that saves a document."
  • "Set up a Logback logging context with Logstash JSON output for my Quarkus app."

What does the skill need to work well?

Reading the skill needs nothing extra. Using the generated code does. The examples assume Java and Quarkus 3.x, plus Apache Camel with the RabbitMQ (spring-rabbitmq) component if you use the messaging patterns, and Lombok, Logback and the Logstash encoder library as used in the examples.

The messaging examples need a RabbitMQ broker to run against. The skill runs no scripts and uses no network access.

  • Java and Quarkus 3.x
  • Apache Camel with the spring-rabbitmq component, for messaging patterns only
  • Lombok, Logback and Logstash encoder libraries
  • A RabbitMQ broker, only to run the messaging examples

What should you check before using the generated code?

The examples are illustrative. The SKILL.md file contains a truncated code sample at the end, and the examples reference classes such as OrderValidator, EventRepository and SecurityContext that exist only in the sample, not in your project. Treat generated code as a draft.

Check every import, dependency version, configuration key and security rule against your own project before you run or deploy it. Ask for a code review as you would for any new code.

  • Confirm that the referenced classes and dependencies exist in your project
  • Verify configuration keys such as the RabbitMQ host and port settings
  • Review transaction boundaries and error handling
  • Test the messaging path against a real or test broker

Tips for getting better results

Name the layer you want, the framework and the messaging broker in your request. Ask the agent to follow the patterns in the skill explicitly if the output drifts from them.

If you do not use Quarkus or Java, do not install this skill. The patterns will not apply, and the agent may try to force them into unrelated code.

  • Say whether you want reactive or classic JAX-RS endpoints
  • Ask for pagination or validation explicitly if you need them
  • Keep the skill in the project folder when the whole team should share the same conventions

What people use it for

  • Scaffolding a Quarkus REST resource, service and repository for a new domain entity
  • Adding a Camel route that sends messages to RabbitMQ from a service method
  • Writing a transactional service that validates input, persists data and records success or error events
  • Setting up Logback logging with a Logstash JSON encoder for a Quarkus service
  • Adding a Camel file-processing route that reads from configured input and processed directories

Frequently asked questions

Is the quarkus-patterns skill free?

The skill is published under the MIT licence, as stated on this page. Check the licence file in the source repository for the full terms before reusing it.

What do I need installed to use it?

You need Java and Quarkus 3.x for the code to make sense. If you use the messaging patterns, you also need Apache Camel with the spring-rabbitmq component, plus Lombok, Logback and the Logstash encoder, and a RabbitMQ broker to run the examples.

Does the skill run scripts or access the network?

No. The skill runs no scripts and uses no network access. It is a SKILL.md file with coding patterns that the agent reads.

Where do I put the skill folder?

Unzip it into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder. In the Claude apps, upload it under Settings → Capabilities → Skills.

Can I use this skill for non-Quarkus projects?

No. The patterns are for Quarkus and Java. In projects that use other frameworks, the patterns will not apply and the agent may force them in.

Why does the generated code fail to compile?

The examples are illustrative and the SKILL.md file ends with a truncated sample. The referenced classes and dependencies must exist in your own project, so check imports, versions and configuration keys before running the code.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use this skill if you build Java services with Quarkus and want an agent to follow a consistent layered style with Camel and RabbitMQ messaging. Pick something else if your project does not use Quarkus or Java, or if you are a non-developer looking for a general tool, since this skill only changes how an agent writes Quarkus code.

Download the skill