spring-modulith
/spring-modulith
Porządkuje monolit Spring Boot w moduły z Spring Modulith, z API modułów, regułami zależności i zdarzeniami.
- Autor
- rrezartprebreza ↗
- Repozytorium
- spring-boot-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 22.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 4
- Skrypty
- 2
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 3
Brak sygnałów. Repozytorium zmienione 22.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 2 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: examples/bad-module-dependency.java, examples/good-module-test.java
Co robi i kiedy
Porządkuje monolit Spring Boot w moduły z Spring Modulith, z API modułów, regułami zależności i zdarzeniami.
Oryginalny opis (EN)
Use when organizing or verifying a modular Spring Boot monolith with Spring Modulith, including module APIs, dependency rules and reliable module events. Do not restructure an application into modules for an unrelated endpoint change.
Jak działa
- Spring Boot 4 baseline
- Apply within the existing architecture
- Verify boundaries
- Reliable events
- Gotchas
- Official sources
Podgląd SKILL.md
--- name: spring-modulith description: > Use when organizing or verifying a modular Spring Boot monolith with Spring Modulith, including module APIs, dependency rules and reliable module events. Do not restructure an application into modules for an unrelated endpoint change. --- # Spring Modulith ## Spring Boot 4 baseline Use the Spring Modulith 2.x line matching the exact Boot 4 minor; do not import a Boot 3 Modulith 1.x BOM. ## Apply within the existing architecture Inspect the application root package, module boundaries and current dependency graph. Use direct subpackages as modules; keep their API at the module root and implementation in internal subpackages. Expose a named interface only for an intentional shared API. Use allowedDependencies when the architecture needs explicit dependency constraints. Avoid creating a generic shared module that every feature depends on. ## Verify boundaries Add spring-modulith-starter-test with test scope and run ApplicationModules.of(Application.class).verify() in CI. It checks cycles and access to module internals. Add ApplicationModuleTest for behavior confined to a module. A passing structure check does not prove transactional or delivery correctness. See [good module verification](examples/good-module-test.java) and [bad cross-module dependency](examples/bad-module-dependency.java). ## Reliable events Publish immutable event payloads containing IDs and necessary facts, not managed JPA entities. Use ApplicationModuleListener for asynchronous transactional listeners when that timing fits. For delivery that must survive a process crash, configure a persistent event publication registry using the chosen JDBC/JPA starter and manage its schema through migrations. An in-memory registry and a plain after-commit callback are not durable delivery. Make handlers idempotent: a crash after the business effect but before recording completion can cause redelivery. Define retry/republication and retention explicitly, and test failed listeners and application restarts. For external brokers, use supported event externalization with persistent publication tracking; do not promise end-to-end exactly-once processing. ## Gotchas - Agent imports a repository from another module's internal package - call its public API or consume an event. - Agent adds Modulith to a simple unrelated task - preserve the requested scope. - Agent assumes ApplicationModuleListener alone guarantees durability - configure persistent publication tracking. - Agent publishes an entity with lazy associations - publish an immutable event contract. - Agent tests only the happy path - verify cycles, module access and event redelivery. ## Official sources - [Module verification](https://docs.spring.io/spring-modulith/reference/verification.html) - [Events and publication registry](https://docs.spring.io/spring-modulith/reference/events.html) - [Compatibility](https://docs.spring.io/spring-modulith/reference/appendix.html)
Pliki w paczce (4)
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
- examples/bad-module-dependency.java 1 KB
- examples/good-module-test.java 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · rrezartprebreza/spring-boot-skills | 100 | MIT |
| claude-dev-suite/claude-dev-suite | 100 | MIT |
| rrezartprebreza/spring-boot-skills | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 66ad1d593f79 (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
- 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-modulith
Wspiera Spring Modulith 2.0 w Spring Boot 4: moduły aplikacji, @ApplicationModuleListener, testy Scenario API, granice modułów, eksport zdarzeń do Kafka i AMQP oraz modularny monolit. - 100spring-modulith-verifier
Sprawdza, czy kod Spring Boot trzyma się struktury pakietów Spring Modulith, i wskazuje naruszenia z sugerowanymi poprawkami. - 80spring-boot-skill
Buduje aplikacje Spring Boot 4.x: REST, JPA, Spring Modulith, Security i Thymeleaf, z testami i strukturą pakietów. - 96add-module
Dodaje nowy moduł aplikacji do projektu Spring Modulith z układem pakietów i testem integracyjnym w zakresie modułu. - 100spring-testing-strategy
Pomaga wybrać rodzaj testu dla kodu Spring Boot: jednostkowy, z kontekstem, wycinkowy, modularny lub przeglądarkowy.