Loading...
Loading...
Found 17 Skills
Get best practices for developing applications with Spring Boot.
Java 开发规范,包含命名约定、异常处理、Spring Boot 最佳实践等
IntelliJ IDEA JetBrains IDE with smart completion. Use for JVM development.
Expert in Java development with Spring Boot and enterprise patterns
Proxy2.0 后端全局编码规范:命名、注释、分层架构、代码风格、依赖注入、复杂度限制等全局约束。 Use when writing, reviewing, or modifying any Java code in the proxy2.0-api project. Triggers on: (1) Creating new Java classes, (2) Code review, (3) Refactoring, (4) Any backend development task in this project.
Upgrade dependencies for Java/Kotlin (Gradle/Maven) and TypeScript/Node projects with minimal risk: plan the bump, apply changes incrementally, run tests/builds, and document breaking changes. Use when the user asks to bump deps, update frameworks, or address CVEs.
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.
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
Use when you need to add or review Flyway database migrations in a Spring Boot application — Maven dependencies, db/migration scripts, spring.flyway.* configuration, baseline and validation, and alignment with JDBC or Spring Data JDBC. Part of the skills-for-java project
Switch JDK, Kotlin, Gradle, Maven, or any SDKMAN-managed candidate when the user or runtime explicitly demands a different version. Use when the user says "switch to Java 17", "run with JDK 21", "use Gradle 8.x", asks about JAVA_HOME, a build fails with UnsupportedClassVersionError or "class file has wrong version", or the repo contains a `.sdkmanrc`. Operates on machines configured with SDKMAN (`$SDKMAN_DIR`, default `~/.sdkman`).
Use when creating git worktrees for Maven projects - prevents SNAPSHOT artifact clashes and corporate plugin resolution failures through isolated local repositories
Expert-level Java development with Java 21+ features, Spring Boot, Maven/Gradle, and enterprise best practices