skills.rest
jdubray
jdubrayCOMMUNITY
Explore all skills by this author →
Website𝕏@metapgmrGitHub

coding-standard-java

Enforce Java naming conventions for variables, methods, classes, and file names.

27|7|Updated Dec 6, 2025
Search Tags:#java#code-quality#coding-standards#naming-conventions#camelCase#pascalCase
One-click install
npx skills add https://github.com/jdubray/puffin --skill coding-standard-java
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coding-standard-java
Source: https://github.com/jdubray/puffin/tree/main/.claude/skills/coding-standard-java
Command: npx skills add https://github.com/jdubray/puffin --skill coding-standard-java

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces Java naming conventions to reduce confusion and improve long-term maintainability by standardizing how code elements are named.

Core Features & Use Cases

  • File naming: Source files must match the public class name (e.g., UserService.java).
  • Naming rules: Variables and methods use camelCase; classes and interfaces use PascalCase; constants use UPPER_SNAKE_CASE.
  • Real-world use: In a multi-module Java project, consistent naming speeds onboarding and review, and reduces refactoring risk.

Quick Start

Apply the Java naming rules to the provided codebase to enforce camelCase, PascalCase, and file-name alignment across the project.

Frequently Asked Questions about coding-standard-java

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

FAQPage Schema
What are the Java naming conventions for variables, methods, and classes?▼

Java naming conventions require camelCase for variables and methods, PascalCase for classes and interfaces, and UPPER_SNAKE_CASE for constants to improve code clarity and maintainability.

How do I enforce consistent Java code quality standards across a multi-module project?▼

You can enforce Java code quality standards by applying consistent naming rules for camelCase, PascalCase, and file-name alignment across code generation, review, and refactoring workflows.

Does a Java source file name need to match the public class name?▼

Yes, Java source files must match the public class name exactly, such as UserService.java, ensuring file-name linkage standardizes project structure and reduces refactoring risks.

What is the correct naming convention for Java constants and test classes?▼

Java constants use UPPER_SNAKE_CASE, while test classes follow PascalCase rules, standardizing element naming to speed up developer onboarding and reduce confusion during code review.

Can I apply Java coding standards to refactoring existing codebases?▼

Yes, Java coding standards can be applied during refactoring to align variable, method, and class names with camelCase and PascalCase rules across projects of any size or architecture.

Related Skills

Explore More Software Engineering Skills→
imMamdouhaboammarimMamdouhaboammar

naming-analyzer

Analyze source code identifiers for naming convention violations across JavaScript, TypeScript, Python, Java, and Go.

Community
Intermediate
CANTAGESTUDIOCANTAGESTUDIO
3

refactor-rename-for-clarity

Rename ambiguous identifiers to descriptive names across languages.

Community
Advanced
AvihusittonAvihusitton

brooks-lint

Review code for design smells, coupling issues, and architectural risks.

Community
Intermediate
JonnyCBBJonnyCBB

code-simplification-common

Apply cross-language simplification patterns to Java, Scala, and Python code.

Community
Intermediate