From java-clean-code
Use when writing, reviewing, or refactoring Java code — services, controllers, libraries, batch jobs, CLIs (Spring Boot, Quarkus, plain Java). Triggers: "clean this up", "is this idiomatic?", code review on Java files, code-smell or technical-debt concerns, SOLID/DRY/SRP questions, TDD setup for Java.
How this skill is triggered — by the user, by Claude, or both
Slash command
/java-clean-code:java-clean-codeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
20 high-ROI rules for Java, with topic references for depth. Same checklist for writing, reviewing, and refactoring.
20 high-ROI rules for Java, with topic references for depth. Same checklist for writing, reviewing, and refactoring.
Writing, reviewing, or refactoring Java classes/methods/endpoints/services; or answering principle questions about Java design.
Skip when: trivial edits, build/config files, non-Java code, or when the user opts out.
Each rule links to a reference file for depth. A subset keeps a Check hint where the name alone is ambiguous.
a.getB().getC().doD() chains on objects (chains on data structures OK). objects-and-data@Autowired field injection is a smell; inject via final constructor params. solidWriting: (1) Name the behavior — if you can't, the design isn't ready. (2) Write the failing test (JUnit 5). (3) Implement minimally, rules 2–6 in mind. (4) Self-check with the checklist below.
Reviewing: (1) Cite each violation by rule name (Demeter, SRP, DIP — never bare "R10") + file:line. (2) Prioritize severity — SRP/Demeter/testing gaps outrank naming nits. (3) Diff-style fixes, each naming the rule. (4) Open references/*.md for rationale.
Each rule links inline to the topic file. Additional depth: smells, architecture, concurrency, craftsmanship, creating-objects, generics, lambdas-and-streams, exceptions.
| Excuse | Counter |
|---|---|
| "One more arg" | Args/Flags: extract a record. |
"Use Lombok @Data" | DIP: write the explicit constructor. |
| "Fine for a demo" | SRP holds under pressure. |
| "Review with bare numbers (R10)" | Cite the rule name + references/*.md. |
Violating the letter of a rule is violating its spirit. Pressure (time, demo, sunk cost) does not suspend the rules — it makes them more valuable.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub nxd1184/java-clean-code-skill --plugin java-clean-code