About this skill

Problem It Solves

Creating a new Spring Boot project by hand can miss Maven layout, package structure, startup class, or configuration files. Adding Knife4j and matching dependencies across Spring Boot versions adds more repetition. This skill turns those setup steps into one parameterized scaffold, giving a clean project that can be extended immediately.

How It Works

It uses parameters such as groupId, artifactId, springBootVersion, and packageName to generate the project structure in the current directory, rather than creating another subfolder. Main outputs include:
- Maven layout: src/main/java, src/main/resources, src/test/java, src/test/resources
- Standard packages: config, controller, service, serviceimpl, entity, mapper, and more
- Base files: pom.xml, application.yml, application class, Knife4jConfig
- Static assets: src/main/resources/static and favicon.ico
- Version mapping: selects compatible Knife4j and related dependency versions for the chosen Spring Boot release

The run validates required parameters first, then writes directories and files. The result is intended as a team scaffold that can later be extended with MyBatis, shared utilities, or business modules.

Boundaries

It produces a base project structure only. It does not include MyBatis Plus, MySQL Connector, Fastjson2, or other dependencies that may be provided by separate skills. If the current directory already contains project files, or the target requires a multi-module layout or custom parent POM, inspect the directory before generating to avoid overwriting existing configuration.

Screenshots

Use Cases

When starting a new Spring Boot microservice, set up the Maven layout, main class, and application.yml.
Initialize a Java service skeleton in the repository root with standard packages and Knife4j documentation config.
Before building an internal tool service, generate pom.xml, src/main layout, and a Knife4jConfig class.
Before standardizing a team service entry point, create a Spring Boot project with base dependencies and static resources.

Best For

Java backend engineers who need a quickly generated Spring Boot skeleton that can be extended immediately.
Server-side developers maintaining internal tool platforms who need unified Maven layout, standard packages, and config files.
Engineers taking over a Spring Boot repository who need the main class, application.yml, and Knife4j setup.
Tech leads defining microservice templates who need initial projects aligned to Spring Boot versions and documentation dependencies.