java-coding-standards

Standardize Java coding practices for Spring Boot services.

24|5|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/Luohaothu/everything-codex --skill java-coding-standards-luohaothu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: java-coding-standards
Source: https://github.com/Luohaothu/everything-codex/tree/main/docs/zh-CN/skills/java-coding-standards
Command: npx skills add https://github.com/Luohaothu/everything-codex --skill java-coding-standards-luohaothu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes Java coding practices for Spring Boot services to improve maintainability and readability.

Core Features & Use Cases

  • Naming conventions, immutability, Optional usage, streams, exception design, generics, and project layout guidelines.
  • Use Case: When onboarding new developers to a Spring Boot project, apply standard patterns to reduce bikeshedding and speed integration.

Quick Start

Follow these Java coding standards to ensure clean, maintainable Spring Boot services.

Frequently Asked Questions about java-coding-standards

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

FAQPage Schema
What are the best Java coding standards for Spring Boot services?

Java coding standards for Spring Boot services enforce naming conventions, immutability, Optional usage, streams, exception design, generics, and project layout. They standardize coding practices to improve maintainability and readability across modules.

How do I enforce immutability and Optional usage in Java code reviews?

To enforce immutability and Optional usage in Java code reviews, apply standard patterns that mandate immutable data structures and proper Optional handling. This reduces bikeshedding and ensures clean, maintainable Spring Boot services.

Does this Java coding standards guidance apply to all Spring Boot modules?

Yes, these Java coding standards apply across all modules in Spring Boot applications running Java 17 or higher. They are designed for use during code reviews, refactoring, and onboarding new developers.

How do I standardize project structure and exception design for Java onboarding?

Standardize project structure and exception design for Java onboarding by applying defined layout guidelines and exception patterns. This speeds up developer integration and reduces bikeshedding on new Spring Boot projects.

Can I use these Java streams and generics guidelines for refactoring legacy code?

Yes, you can use these Java streams and generics guidelines during refactoring to ensure clean, immutable coding. They provide standard patterns to improve maintainability and readability for existing Spring Boot services.