agentsclimarketplace
Sign in

Claude skills for quarkus

Skill autohandai/community-skills/claude-skills-for-quarkus

Use Claude skills for Quarkus to build domain-driven Quarkus applications and Java modernization workflows.From its SKILL.md

Install
npx -y skills add autohandai/community-skills --skill claude-skills-for-quarkus

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 9 stars9 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 file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.7 KB, 302 tokens by cl100k_base, as published. Nobody here has run it

Claude Skills for Quarkus

Overview

Use this skill when a Java repository needs Quarkus and domain-driven design guidance from jeremyrdavis/claude-skills-for-quarkus. The upstream project focuses on building Quarkus applications with DDD-oriented agent support.

Compatibility: Quarkus, Java, domain-driven design, Maven, REST services, and modernization workflows.

Workflow

  1. Identify the Quarkus version, Java version, extension set, persistence layer, and runtime target.
  2. Map the domain model before generating resources, services, repositories, or adapters.
  3. Keep Quarkus idioms intact: configuration, CDI, REST endpoints, Panache or repository patterns, and test profiles.
  4. For modernization, define the source framework and target Quarkus boundary before conversion.
  5. Validate with the repository's Maven or Gradle commands and Quarkus tests.

Guardrails

  • Do not flatten domain boundaries into CRUD-only services unless the project already follows that style.
  • Preserve API contracts, database migrations, and configuration property semantics.
  • Check the upstream README before reusing Quarkus-specific instructions because supported patterns may change.
  • Keep native-image assumptions separate from standard JVM runtime behavior.

Expected Output

Return a Quarkus-focused plan or implementation with domain boundaries, affected files, validation commands, and migration risks.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,422. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.