java-coding-standards

Enforce Java 17+ coding standards for Spring Boot and Quarkus services.

26|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/BinyaminEden/claude-combine --skill java-coding-standards-binyamineden
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: java-coding-standards
Source: https://github.com/BinyaminEden/claude-combine/tree/main/skills/java-coding-standards
Command: npx skills add https://github.com/BinyaminEden/claude-combine --skill java-coding-standards-binyamineden

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates inconsistent, hard-to-maintain Java code in Spring Boot and Quarkus services by enforcing framework-specific and shared coding conventions, reducing technical debt and speeding up team onboarding.

Core Features & Use Cases

  • Framework-Aware Standards: Automatically applies separate conventions for Spring Boot and Quarkus based on build file detection, covering naming, immutability, dependency injection, and reactive patterns.
  • Java 17+ Best Practices: Includes guidelines for records, sealed classes, pattern matching, Optional usage, and stream best practices.
  • Use Case: When reviewing a new Quarkus microservice, use this Skill to validate that all JAX-RS resources are named *Resource (not *Controller), use constructor injection, and avoid blocking calls in reactive Uni pipelines.

Quick Start

Use the java-coding-standards skill to review the attached OrderService.java file for compliance with Quarkus coding conventions and suggest improvements for reactive pipeline safety and CDI injection patterns.

Frequently Asked Questions about java-coding-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce Java coding standards for Spring Boot and Quarkus services?

To enforce Java coding standards for Spring Boot and Quarkus, apply framework-specific conventions for naming, immutability, dependency injection, and reactive patterns. This ensures consistent code quality and reduces technical debt across Java 17+ microservices.

What are the Java 17 best practices for records and sealed classes in Spring Boot?

Java 17 best practices for Spring Boot include using records for immutability, sealed classes for restricted hierarchies, pattern matching, and proper Optional usage. These practices improve code maintainability and align with standardized coding conventions.

Does this coding standard work with both Spring Boot and Quarkus frameworks?

Yes, it applies separate conventions for Spring Boot and Quarkus based on build file detection. It validates framework-specific layouts, ensuring correct JAX-RS Resource naming for Quarkus and appropriate dependency injection patterns for each framework.

How do I review a Quarkus microservice for reactive pipeline safety?

To review a Quarkus microservice for reactive pipeline safety, validate that JAX-RS resources use constructor injection and avoid blocking calls within reactive Uni pipelines. This ensures compliance with CDI injection patterns and reactive programming standards.

What is the correct naming convention for JAX-RS resources in Quarkus?

The correct naming convention for JAX-RS resources in Quarkus requires naming classes as *Resource instead of *Controller. This distinguishes them from Spring Boot components and aligns with framework-specific project layout conventions.