coding-standard-java
Java Coding Standards
When reviewing or generating Java code, follow these rules:
File Naming
- Source files: PascalCase matching the public class name (e.g.,
UserService.java) - One public class per file: File name must match the public class name exactly
- Test files: Class name with
Testsuffix (e.g.,UserServiceTest.java) - Interface files: PascalCase (e.g.,
Comparable.java,UserRepository.java)
Package Naming
- Packages: All lowercase, dot-separated (e.g.,
com.example.service,org.project.utils) - No underscores or hyphens in package names
- Follow reverse domain name convention
More from jdubray/puffin
coding-standard-cpp
Enforce C++ coding standards including camelCase or snake_case variables, PascalCase classes, and consistent file naming.
26coding-standard-python
Enforce Python PEP 8 coding standards including snake_case variables, PascalCase classes, and snake_case filenames.
20coding-standard-javascript
Enforce JavaScript/ES6+ and TypeScript coding standards including camelCase variables, PascalCase classes, and kebab-case filenames.
18modularity-patterns
Recommends modularity, composition, and decoupling patterns for design challenges. Use when designing plugin architectures, reducing coupling, improving testability, or separating cross-cutting concerns.
17coding-standard-c
Enforce C coding standards including snake_case variables and functions, UPPER_SNAKE_CASE macros, and snake_case filenames.
16rlm
Run a Recursive Language Model-style loop for long-context tasks. Uses a persistent local Python REPL and an rlm-subcall subagent as the sub-LLM (llm_query).
1