Loading...
Loading...
Found 22 Skills
Expert-level Java development with Java 21+ features, Spring Boot, Maven/Gradle, and enterprise best practices
Use when you need to find which JAR contains a Java class, resolve import statements, identify classpath conflicts, or discover which dependency provides a class. Accepts fully qualified class names, simple class names, or partial patterns.
Expert in Java development with Spring Boot and enterprise patterns
Use when you need to generate a checklist document with Java system prompts, following the embedded template exactly and producing INVENTORY-SKILLS-JAVA.md in the project root. Part of the skills-for-java project
Look up the public API of any JVM dependency (Scala 3, Scala 2, Java) from the terminal — type signatures, members, docs, and source as Markdown, no JAR unpacking needed. Use this skill whenever you need to call an unfamiliar library method, explore a package's types, or check a dependency's API. Prefer cellar over Metals MCP only for looking up external dependency APIs (`cellar get-external` vs Metals `inspect`/`get-docs`) — cellar needs no project import and queries any published Maven artifact. For everything else (references, rename, goto definition, diagnostics, compile), use Metals.
Generate conventional commit messages for Java projects. Use when user says "commit", "create commit", "commit changes", or after completing code changes that need to be committed.
Java and Spring Boot expert including REST APIs, JPA, and microservices
Use when creating git worktrees for Maven projects - prevents SNAPSHOT artifact clashes and corporate plugin resolution failures through isolated local repositories
Enterprise Java development skill covering Spring ecosystem, microservices, design patterns, performance optimization, and Java best practices. Use this skill when building enterprise Java applications, working with Spring Boot, implementing microservices, or need guidance on Java architecture and performance tuning.
Alibaba Java Development Manual (Huangshan Edition 1.7.1) - When writing or reviewing Java code, defining coding standards, handling exceptions and logs, writing unit tests, designing database tables and indexes, or planning engineering layers or system architecture, locate the conventions that should be followed for the relevant scenario. The detailed convention text is in the references/ directory.