Przejdź do treści
Biblioteka skilli
Programowanie · Budowanie i kod

spring-boot-skill

/spring-boot-skill

Buduje aplikacje Spring Boot 4.x: REST, JPA, Spring Modulith, Security i Thymeleaf, z testami i strukturą pakietów.

Licencja
MIT
Ostatnia zmiana repozytorium
12.10.2026

Ocena i bezpieczeństwo

80/ 100Klasa: dobry
Format20 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść20 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
20
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 12.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Buduje aplikacje Spring Boot 4.x: REST, JPA, Spring Modulith, Security i Thymeleaf, z testami i strukturą pakietów.

Oryginalny opis (EN)

Build Spring Boot 4.x applications following the best practices. Use this skill: * When developing Spring Boot applications using Spring MVC, Spring Data JPA, Spring Modulith, Spring Security * To create recommended Spring Boot package structure * To implement REST APIs, entities/repositories, service layer, modular monoliths * To use Thymeleaf view templates for building web applications * To write tests for REST APIs and Web applications * To write ArchUnit tests for testing architecture * To configure the recommended plugins and configurations to improve code quality, and testing while usin

Jak działa

  1. Maven pom.xml Configuration
  2. Package structure
  3. Spring Data JPA
  4. Service layer
  5. Spring MVC REST APIs
  6. Spring Modulith
  7. Thymeleaf
  8. Testing
  9. Taskfile
Sekcje z nagłówków SKILL.md, w oryginale · 67 linii, 434 słów
Podgląd SKILL.md
---
name: spring-boot-skill
description: >
  Build Spring Boot 4.x applications following the best practices. 
  Use this skill:
    * When developing Spring Boot applications using Spring MVC, Spring Data JPA, Spring Modulith, Spring Security
    * To create recommended Spring Boot package structure
    * To implement REST APIs, entities/repositories, service layer, modular monoliths
    * To use Thymeleaf view templates for building web applications
    * To write tests for REST APIs and Web applications
    * To write ArchUnit tests for testing architecture
    * To configure the recommended plugins and configurations to improve code quality, and testing while using Maven.
    * To use Spring Boot's Docker Compose support for local development
    * To create Taskfile for easier execution of common tasks while working with a Spring Boot application
---

# Spring Boot Skill

Apply the practices below when developing Spring Boot applications. Read the linked reference only when working on that area.

## Maven pom.xml Configuration

Read [references/spring-boot-maven-config.md](references/spring-boot-maven-config.md) for Maven `pom.xml` configuration with supporting plugins and configurations to improve code quality, and testing.

## Package structure

Read [references/code-organization.md](references/code-organization.md) for domain-driven, module-based package layout and naming conventions.

## Spring Data JPA

Implement the repository and entity layer using [references/spring-data-jpa.md](references/spring-data-jpa.md).

## Service layer

Implement business logic in the service layer using [references/spring-service-layer.md](references/spring-service-layer.md).

## Spring MVC REST APIs

Implement REST APIs with Spring MVC using [references/spring-webmvc-rest-api.md](references/spring-webmvc-rest-api.md).

## Spring Modulith

Build a modular monolith with Spring Modulith using [references/spring-modulith.md](references/spring-modulith.md).

## Thymeleaf

If Thymeleaf is used for view templates, refer [references/thymeleaf.md](references/thymeleaf.md)

## Testing

Write tests at complementary levels — unit, sliced Spring tests, and at least one end-to-end/smoke test; the levels are not either/or. Most framework-touching tests belong at the fast **sliced** level (`@SpringBootTest(classes = …)` or a slice annotation); keep full-context `@SpringBootTest` for a smoke test plus a request-level end-to-end. For why the levels are complementary and how to keep a large suite fast (context caching, one container for the suite), read [references/testing-strategy.md](references/testing-strategy.md).

| What you're testing                                                                        | Level                                                   | Reference                                                                                                       |
|--------------------------------------------------------------------------------------------|---------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|
| Business/domain logic, no framework                                                        | Unit (no Spring context)                                | [testing-unit-mocking.md](references/testing-unit-mocking.md)                                                   |
| JPA / JDBC / JdbcClient / Spring Data JDBC / jOOQ queries                                  | Persistence slice + Testcontainers                      | [testing-slices-persistence.md](references/testing-slices-persistence.md)                                       |
| Controller, JSON serialization, or a REST client                                           | Web slice (`@WebMvcTest`/`@JsonTest`/`@RestClientTest`) | [testing-slices-web.md](references/testing-slices-web.md)                                                       |
| A few components together, external HTTP (WireMock), or a startup/request-level smoke test | Sliced `@SpringBootTest(classes = …)` or smoke test     | [testing-integration.md](references/testing-integration.md)                                                     |
| Full REST API over a real port, full `BaseIT` suite (`RestTestClient`)                     | End-to-end                                              | [spring-boot-rest-api-testing.md](references/spring-boot-rest-api-testing.md)                                   |
| A view-rendering controller (`MockMvcTester`)                                              | Web slice                                               | [spring-boot-webapp-testing-with-mockmvctester.md](references/spring-boot-webapp-testing-with-mockmvctester.md) |
| Wiring a container (`@ServiceConnection` / dynamic properties)                             | —                                                       | [testcontainers-wiring.md](references/testcontainers-wiring.md)                                                 |

All persistence and integration tests use **Testcontainers with a real database** (never in-memory H2); see [references/testcontainers-wiring.md](references/testcontainers-wiring.md) for `@ServiceConnection` vs dynamic-property wiring.

### Test Data Setup

Prefer SQL fixtures with `@Sql("classpath:/test-data.sql")` before every test method. 
When setting up data programmatically, prefer exposed Services or ModuleAPI classes over Repositories, `JdbcTemplate`, or `JdbcClient`. 
Unless absolutely necessary, avoid using `JdbcTemplate`, `JdbcClient`, or `TransactionTemplate` 
to execute SQL for test data setup, which couples tests to internal implementation details. 
Read [references/test-data-setup.md](references/test-data-setup.md) when creating or changing test fixtures.

### Write ArchUnit Tests
To write tests for testing the architecture using ArchUnit, refer [references/archunit.md](references/archunit.md)

### Spring Boot Docker Compose Support
To use Docker Compose support for local development, refer [references/spring-boot-docker-compose.md](references/spring-boot-docker-compose.md).

## Taskfile

Use [references/taskfile.md](references/taskfile.md) for easier commands execution.
Pliki w paczce (20)
  • SKILL.md 6 KB
  • references/archunit.md 3 KB
  • references/code-organization.md 5 KB
  • references/spring-boot-docker-compose.md 1 KB
  • references/spring-boot-maven-config.md 5 KB
  • references/spring-boot-rest-api-testing.md 9 KB
  • references/spring-boot-webapp-testing-with-mockmvctester.md 4 KB
  • references/spring-data-jpa.md 7 KB
  • references/spring-modulith.md 4 KB
  • references/spring-service-layer.md 3 KB
  • references/spring-webmvc-rest-api.md 8 KB
  • references/taskfile.md 2 KB
  • references/test-data-setup.md 2 KB
  • references/testcontainers-wiring.md 7 KB
  • references/testing-integration.md 11 KB
  • references/testing-slices-persistence.md 5 KB
  • references/testing-slices-web.md 4 KB
  • references/testing-strategy.md 8 KB
  • references/testing-unit-mocking.md 3 KB
  • references/thymeleaf.md 3 KB

Wersje

W bazie nie ma innych skilli o nazwie spring-boot-skill.

Identyczna treść występuje jeszcze w 1 innych folderach na GitHubie. Tu pokazujemy jedną, najlepiej ocenioną kopię.

Migawka bazy z 13.11.2026 · wersja paczki 2e3762187d5d (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100spring-boot
    Wspiera tworzenie w Spring Boot 4 REST API, warstwy JPA, bezpieczeństwa, testów i usług chmurowych.
  • 90java-spring-boot-expert
    Pomaga budować aplikacje Spring Boot 3.x, mikroserwisy i reaktywne aplikacje Java, z Spring Data JPA i Spring Security 6.
  • 100spring-modulith-verifier
    Sprawdza, czy kod Spring Boot trzyma się struktury pakietów Spring Modulith, i wskazuje naruszenia z sugerowanymi poprawkami.
  • 100305-frameworks-spring-boot-modulith
    Projektuje i sprawdza modularne monolity w Spring Modulith: pakiety modułów, zależności, zdarzenia domenowe i testy modułów.
  • 100spring-boot-engineer
    Generuje konfiguracje Spring Boot 3.x, kontrolery REST, uwierzytelnianie Spring Security 6, repozytoria JPA i endpointy WebFlux.
  • 100spring-boot
    Wspiera budowę aplikacji w Spring Boot 4 (Spring Framework 7): REST API z JPA i Flyway, zabezpieczenia JWT, Actuator i testy MockMvc.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.