Java Coding Standards
Write and review Java 17+ with Muse: Spring Boot and Quarkus conventions, naming, records and immutability, Optional, streams, dependency injection, reactive patterns, exceptions, project layout, and tests.
- What
- Write and review Java 17+ with Muse: Spring Boot and Quarkus conventions, naming, records and immutability, Optional, streams, dependency injection, reactive patterns, exceptions, project layout, and tests.
- Cost
- Free
- Needs
- Use "Java Coding Standards" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a Java coding-standards guide that makes Muse write and review Java 17+ the way each framework expects. It starts by detecting your framework from the build file (quarkus, spring-boot, or shared Java conventions only) and applies the right conventions automatically. Naming covers PascalCase classes and records, camelCase methods and fields, UPPER_SNAKE_CASE constants, plus the framework split: *Resource for Quarkus JAX-RS endpoints, *Controller for Spring. Immutability favors records and final fields, with the deliberate Quarkus exception for Panache active-record entities where public fields are idiomatic. Optional usage covers find* methods returning Optional with map and flatMap instead of get(). Streams get the rule for short pipelines, loops for clarity when it gets complex. Dependency injection prefers constructor injection in both frameworks, flags Spring field injection with @Autowired as a fail, and warns against @Singleton where @ApplicationScoped is needed in Quarkus. Reactive patterns cover Uni and Multi pipelines, failWith on null, and the blocking-call-inside-Uni trap. Exceptions get domain-specific unchecked exceptions with centralized handlers (RestControllerAdvice in Spring, ExceptionMapper or @ServerExceptionMapper in Quarkus). Generics, per-framework project layout, logging (SLF4J versus JBoss), configuration (@ConfigurationProperties versus @ConfigMapping), and testing expectations (@WebMvcTest and @DataJpaTest slices in Spring, plain JUnit plus @QuarkusTest integration tests with Dev Services in Quarkus) round it out. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: it assumes Java 17+ (records, sealed classes, pattern matching), so check your version first; it is guidance, not a compiler, so your build and tests remain the final word. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Java Coding Standards" with your Muse. Prerequisites: none to install. Pure guidance; a Java 17+ Spring Boot or Quarkus project helps. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/java-coding-standards/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Review this Java code against the standards for my framework: [paste code, and mention Spring Boot or Quarkus]." 3. Ask follow-ups like "rewrite this with constructor injection and records" or "spot the blocking call inside the Uni pipeline." Tip: tell Muse your framework up front so it applies the Spring or Quarkus conventions, not the shared ones only. Safety: a skill is plain-text instructions; it runs nothing by itself. Review generated commands before running them.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.