Skip to main content
skill CX Codex

403-frameworks-quarkus-validation — Claude Code skill

403-frameworks-quarkus-validation guides Quarkus validation work, from DTO constraints and REST boundaries to configuration checks and API error mapping.

Apache-2.0 296 installs ★ 465 updated 2026-10-21

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jabrena/plinth --skill 403-frameworks-quarkus-validation -a claude-code
Open on GitHub

What 403-frameworks-quarkus-validation does

The skill guides Bean Validation work in Quarkus applications. It covers constraints on DTOs and command models, @Valid in REST resources, validation groups, and custom constraints. It also addresses nested DTOs, @ConfigMapping checks, and mapping validation failures through ExceptionMapper.

The agent first reads references/403-frameworks-quarkus-validation.md and inspects the project. Before changing anything, it must run ./mvnw compile or mvn compile; a failed compile means stop. After the changes, the skill calls for ./mvnw clean verify or mvn clean verify. A project that does not compile is therefore a blocker for validation changes.

What it helps with

  • add Bean Validation constraints to DTOs and command models
  • check @Valid usage in REST resources
  • define validation groups and custom constraints
  • validate @ConfigMapping properties
  • map validation failures to API responses with ExceptionMapper

Example prompts for the agent

  • Add validation to the request DTOs in this Quarkus REST API and verify the changes.
  • Review the Bean Validation rules and @Valid usage in this project.
  • Check the @ConfigMapping properties and map validation failures through ExceptionMapper.

How to install 403-frameworks-quarkus-validation

1Skills CLI (Vercel)

npx skills add jabrena/plinth --skill 403-frameworks-quarkus-validation -a claude-code

2Manually: put the files in place

~/.claude/skills/403-frameworks-quarkus-validation/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/403-frameworks-quarkus-validation/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about 403-frameworks-quarkus-validation

How do I install 403-frameworks-quarkus-validation in Claude Code?

Run npx skills add jabrena/plinth --skill 403-frameworks-quarkus-validation -a claude-code. The skill file is at ~/.claude/skills/403-frameworks-quarkus-validation/SKILL.md.

What does 403-frameworks-quarkus-validation do?

It guides validation changes in Quarkus, including DTO constraints, @Valid at REST boundaries, configuration checks, and API error mapping.

What must I check before changing validation rules?

Read references/403-frameworks-quarkus-validation.md, then run ./mvnw compile or mvn compile. If compilation fails, stop; after making changes, run ./mvnw clean verify or mvn clean verify.

Source text

SKILL.md · Apache-2.0
---
name: 403-frameworks-quarkus-validation
description: Use when you need to design, review, or improve validation in Quarkus applications — including Bean Validation on JAX-RS resources, @Valid on parameters and CDI beans, constraint groups, @ConfigMapping validation, custom constraints, nested DTO validation, and ExceptionMapper-based error mapping. This should trigger for requests such as Add validation support in Quarkus; Review Quarkus validation rules; Improve request validation in Quarkus REST APIs; Add custom validation constraints in Quarkus; Validate Quarkus @ConfigMapping properties. Part of Plinth Toolkit
license: Apache-2.0
metadata:
  author: Juan Antonio Breña Moral
  version: 0.19.0
---
# Quarkus Validation Guidelines

Apply Quarkus validation best practices at REST boundaries.

**What is covered in this Skill?**

- Bean Validation annotations on DTOs and command models
- @Valid and boundary validation in Jakarta REST resources
- Validation groups and custom constraints
- Validation error mapping for client-safe responses
- Consistent handling of invalid inputs across endpoints

**Scope:** Apply recommendations based on the reference rules and good/bad examples.

## Constraints

Before applying validation changes, ensure the project compiles. After improvements, run full verification.

- **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any change
- **SAFETY**: If compilation fails, stop immediately
- **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements
- **BEFORE APPLYING**: Read the reference for detailed rules and examples

## When to use this skill

- Add validation support in Quarkus
- Review Quarkus validation rules
- Improve request validation in Quarkus REST APIs
- Add custom validation constraints in Quarkus
- Validate Quarkus @ConfigMapping properties
- Improve validation error mapping with ExceptionMapper in Quarkus

## Workflow

1. **Read reference and assess project context**

Read `references/403-frameworks-quarkus-validation.md` and inspect the current project setup before proposing changes.

2. **Gather scope and decide target improvements**

Identify requested outcomes, constraints, and the minimum safe set of changes to apply.

3. **Apply framework-aligned changes**

Implement or refactor validation-related configuration/code following the reference patterns and project conventions.

4. **Run verification and report results**

Execute appropriate build/tests and summarize what changed, what was verified, and any follow-up actions.

## Reference

For detailed guidance, examples, and constraints, see [references/403-frameworks-quarkus-validation.md](references/403-frameworks-quarkus-validation.md).

© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth

Similar skills

All skills for Backend and APIs →

From the same set123

The whole set →
126-java-exception-handling 126-java-exception-handling is a Claude Code skill for Java exception handling. It activates on requests to review error types, resource cleanup, or failure propagation. CX Codex +1 307installs 703-technologies-fuzzing-testing The 703-technologies-fuzzing-testing skill guides CATS-based fuzz testing for Java APIs from an OpenAPI contract. Use it to probe invalid inputs, boundary conditions, and CI checks. CX Codex +1 304installs 314-frameworks-spring-kafka 314-frameworks-spring-kafka guides Kafka messaging setup in Spring Boot projects, covering consumers, DLT retries, and Testcontainers. CX Codex +1 297installs 182-java-observability-metrics-micrometer 182-java-observability-metrics-micrometer guides Java developers through Micrometer metrics design and validation. Use it when adding service measurements or revising existing instrumentation. CX Codex +1 297installs 404-frameworks-quarkus-security 404-frameworks-quarkus-security is a skill for designing and reviewing security in Quarkus applications, including authentication, access control, and secure logging. CX Codex +1 294installs 315-frameworks-spring-mongodb 315-frameworks-spring-mongodb — a skill for designing and implementing MongoDB data access in Spring Boot. Covers document modeling, repositories, indexing, optimistic locking, and error handling strategies. CX Codex +1 284installs 504-frameworks-micronaut-security The 504-frameworks-micronaut-security skill reviews and improves Micronaut application security, covering authentication, route authorization, JWT, CORS, and safe handling of sensitive data. CX Codex +1 282installs 503-frameworks-micronaut-validation 503-frameworks-micronaut-validation guides validation setup in Micronaut applications, from Bean Validation annotations to HTTP 400 error payloads. CX Codex +1 280installs

Project sponsors

Companies that keep this analytics open