402-frameworks-quarkus-rest

Use when you need to design, review, or improve REST APIs with Quarkus REST (Jakarta REST) — including resource classes, HTTP methods, status codes, request/response DTOs, Bean Validation, exception mappers, optional runtime OpenAPI exposure (SmallRye), contract-first generation from OpenAPI, content negotiation, pagination, sorting and filtering, API versioning, idempotency (Idempotency-Key), optimistic concurrency (ETag / If-Match), HTTP caching (Cache-Control), API deprecation (Sunset / Deprecation headers), RFC 7807 Problem Details, ISO-8601 for time in contracts, and security-aware boundaries. This should trigger for requests such as Review or improve JAX-RS resources in a Quarkus project; Design HTTP APIs with validation and error handling on Quarkus; Add API versioning, idempotency, ETag concurrency, or deprecation headers; Implement pagination, sorting, or RFC 7807 Problem Details error responses. Part of cursor-rules-java project

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-structured with a clear validated workflow and clean one-level progressive disclosure. Its main weakness is actionability: it offers concrete build/verify commands but no code examples for the REST design work itself, leaving the actionable detail entirely in the reference file.

Suggestions

Add one or two compact, executable code snippets in the body (e.g., a minimal @Path resource with Bean Validation, or an ExceptionMapper returning RFC 7807 Problem Details) so the skill provides concrete guidance without forcing a reference lookup.

Consolidate the redundant compile-gate statements in the Constraints section (MANDATORY/PREREQUISITE/SAFETY/BLOCKING CONDITION) into a single clear rule to tighten token usage.

Include a brief inline decision aid (e.g., when to use URI-path vs Accept-header versioning) so the body carries at least one actionable rule rather than only deferring to the reference.

Dimension	Reasoning	Score
Conciseness	The body is lean and bullet-driven with no concept-explanation padding, assuming Claude's competence; the only minor redundancy is the Constraints section restating 'must compile before changes' in several labeled variants, which is not enough to drop it below the 'lean and efficient' anchor.	3 / 3
Actionability	Verification commands (./mvnw compile, mvn clean verify) and the reference path are concrete, but the body provides no executable code or concrete examples for the skill's actual subject matter (resource classes, ExceptionMappers, DTOs), deferring all detail to the reference with abstract phrasing like 'Apply framework-aligned changes following the reference patterns'.	2 / 3
Workflow Clarity	A clear four-step sequence is paired with explicit mandatory validation checkpoints (compile before changes, stop immediately on failure, verify after changes), matching the 'clear sequence with explicit validation steps; feedback loops' anchor.	3 / 3
Progressive Disclosure	The body acts as an overview pointing to a single, verified, one-level-deep reference (references/402-frameworks-quarkus-rest.md, linked as markdown), with detailed rules/examples appropriately split out and easy to navigate.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, comprehensive, and clearly scoped to Quarkus REST APIs with explicit 'Use when' triggers and natural user-request phrasing. It uses third-person/imperative voice with no over-claims.

Dimension	Reasoning	Score
Specificity	Lists many concrete capabilities (resource classes, HTTP methods, DTOs, Bean Validation, exception mappers, pagination, idempotency, ETag concurrency, RFC 7807 Problem Details, etc.), matching the 'lists multiple specific concrete actions' anchor and exceeding the partial-coverage anchor.	3 / 3
Completeness	Explicitly answers both what (the extensive capability inventory) and when (the 'Use when...' clause plus the 'This should trigger for requests such as' examples), matching the 'clearly answers both what AND when' anchor.	3 / 3
Trigger Term Quality	Trigger examples are phrased as natural user requests ('Review or improve JAX-RS resources...', 'Design HTTP APIs...', 'Add... headers', 'Implement... error responses'), giving good coverage of terms users would actually say rather than just jargon.	3 / 3
Distinctiveness Conflict Risk	Narrowly scoped to REST APIs on Quarkus/JAX-RS, with distinct Quarkus-specific triggers unlikely to fire for unrelated skills; matches the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/cursor-rules-java
Commit: 89b82c7

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.