a-pavithraa/springboot-skills-marketplace / plugins/springboot-architecture/skills/creating-springboot-projects
creating-springboot-projects
VerifiedUse when starting a new Spring Boot project or service: scaffolding or bootstrapping a backend, REST API, microservice or modular monolith; choosing how to structure it (layered, package-by-module, modular monolith, tomato, DDD-hexagonal); selecting Spring Boot 4 features; generating the base project with progen or Spring Initializr; or applying the bundled templates and references in this skill. Not for migrating existing projects or for isolated JPA/repository work without broader project-creation context.
assets/pom-additions.xml
View on GitHub<!--
Additional POM dependencies for Spring Boot projects.
Add these to your pom.xml as needed.
-->
<!-- ============================================================ -->
<!-- TSID - For application-generated IDs (Tomato/DDD patterns) -->
<!-- ============================================================ -->
<!-- Spring Boot 4.1.x ships Hibernate 7.4.x. hypersistence-utils has no -hibernate-74
module yet, so use the newest published one, -hibernate-73 (verify it runs against 7.4.x).
Confirm latest version: https://central.sonatype.com/artifact/io.hypersistence/hypersistence-utils-hibernate-73/versions -->
<dependency>
<groupId>io.hypersistence</groupId>
<artifactId>hypersistence-utils-hibernate-73</artifactId>
<version>3.15.3</version>
</dependency>
<!-- Usage:
package {{PACKAGE}}.shared;
import io.hypersistence.tsid.TSID;
public class TSIDUtil {
private TSIDUtil() {}
public static String generateTsidString() {
return TSID.Factory.getTsid().toString();
}
public static Long generateTsidLong() {
return TSID.Factory.getTsid().toLong();
}
}
-->
<!-- ============================================================ -->
<!-- Spring Modulith - For Modular Monolith/Tomato patterns -->
<!-- ============================================================ -->
<dependency>
<groupId>org.springframework.modulith</groupId>
<artifactId>spring-modulith-starter-core</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.modulith</groupId>
<artifactId>spring-modulith-starter-jpa</artifactId>
</dependency>
<!-- Add to dependencyManagement:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.springframework.modulith</groupId>
<artifactId>spring-modulith-bom</artifactId>
<version>2.1.0</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
-->
<!-- ============================================================ -->
<!-- ArchUnit - architecture tests for every style -->
<!-- ============================================================ -->
<!-- The rules are the team harness's CodeRulesTests (Step 6 of SKILL.md). apply_harness.py adds this
dependency to Maven projects; add it by hand only for Gradle or the onion rule below. -->
<dependency>
<groupId>com.tngtech.archunit</groupId>
<artifactId>archunit</artifactId>
<version>1.5.1</version>
<scope>test</scope>
</dependency>
<!-- DDD+Hexagonal: add an onion rule with ArchUnit's core API. Usage:
@ParameterizedTest
@ValueSource(strings = {"products", "orders"})
void shouldVerifyHexagonalArchitecture(String moduleName) {
JavaClasses classes = new ClassFileImporter()
.importPackages("com.example.%s".formatted(moduleName));
onionArchitecture()
.domainModels("com.example.%s.domain..".formatted(moduleName))
.applicationServices("com.example.%s.application..".formatted(moduleName))
.adapter("persistence", "com.example.%s.infra.persistence..".formatted(moduleName))
.adapter("rest", "com.example.%s.interfaces.rest..".formatted(moduleName))
.check(classes);
}
-->
<!-- ============================================================ -->
<!-- Testcontainers 2.x - For integration tests -->
<!-- ============================================================ -->
<!--
Testcontainers 2.0 (GA Oct 14, 2025) renamed all module artifacts with the
`testcontainers-` prefix and relocated container classes to
`org.testcontainers.<module>` packages. Update imports accordingly:
org.testcontainers.containers.PostgreSQLContainer
-> org.testcontainers.postgresql.PostgreSQLContainer
-->
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-testcontainers</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.testcontainers</groupId>
<artifactId>testcontainers-junit-jupiter</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.testcontainers</groupId>
<artifactId>testcontainers-postgresql</artifactId>
<scope>test</scope>
</dependency>
<!-- Or for MySQL:
<dependency>
<groupId>org.testcontainers</groupId>
<artifactId>testcontainers-mysql</artifactId>
<scope>test</scope>
</dependency>
-->
<!-- ============================================================ -->
<!-- SpringDoc OpenAPI - For Swagger UI -->
<!-- ============================================================ -->
<dependency>
<groupId>org.springdoc</groupId>
<artifactId>springdoc-openapi-starter-webmvc-ui</artifactId>
<!-- Set version per Springdoc release notes -->
<version>${springdoc.version}</version>
</dependency>
<!-- Access at: http://localhost:8080/swagger-ui.html -->
<!-- ============================================================ -->
<!-- Spring Boot 4 Features & Improvements -->
<!-- ============================================================ -->
<!--
Spring Boot 4 highlights (see release notes and reference docs):
1. RestTestClient - Modern REST testing API
- Template: resttestclient-test.java
2. HTTP Service Clients
- Template: http-service-client.java
- Auto-configuration and properties are provided by Spring Boot.
3. API Versioning (Spring MVC / WebFlux)
- Template: api-versioning-config.java
- Property-based configuration is supported (spring.mvc.apiversion.*).
4. OpenTelemetry starter
- Dependency: spring-boot-starter-opentelemetry
5. Kotlin serialization
- Module: spring-boot-kotlinx-serialization-json
- Starter: spring-boot-starter-kotlin-serialization
6. JmsClient support
- JMS auto-configuration includes the new JmsClient API.
7. TaskDecorator composition
- Multiple TaskDecorator beans are supported via CompositeTaskDecorator.
8. JSpecify null-safety improvements
- Template: package-info-jspecify.java
Native resilience (@Retryable, @ConcurrencyLimit, RetryTemplate) is official in
Spring Framework 7 — see https://spring.io/blog/2025/09/09/core-spring-resilience-features/
and the EnableResilientMethods Javadoc. A community sample sits at
https://github.com/sivaprasadreddy/spring-boot-4-features/tree/main/resilience-features
for additional patterns, but Spring's blog and Javadoc are the primary references.
-->
<!-- ============================================================ -->
<!-- Spring Boot 4 AOT Configuration (for Native Images) -->
<!-- ============================================================ -->
<!--
Add this to enable ahead-of-time compilation:
<build>
<plugins>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<executions>
<execution>
<id>process-aot</id>
<goals>
<goal>process-aot</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
-->
<!-- ============================================================ -->
<!-- JSpecify Dependency (Optional - for additional tooling) -->
<!-- ============================================================ -->
<!--
JSpecify is included by default in Spring Boot 4.
Add this only if you need explicit version control:
<dependency>
<groupId>org.jspecify</groupId>
<artifactId>jspecify</artifactId>
<version>1.0.0</version>
<scope>provided</scope>
</dependency>
Usage:
1. Create package-info.java in each package
2. Add @NullMarked annotation
3. Configure IDE for null safety warnings
4. Use @Nullable for optional fields
See template: package-info-jspecify.java
-->
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |