305-frameworks-spring-boot-modulith
This skill provides guidance for designing and improving modular monolith architectures in Spring Boot applications using Spring Modulith. Use it when adding Spring Modulith to projects, reviewing module boundaries, implementing domain events, creating architecture tests with @ApplicationModuleTest, or generating module documentation and observability configurations.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/305-frameworks-spring-boot-modulith && cp -r /tmp/305-frameworks-spring-boot-modulith/skills/305-frameworks-spring-boot-modulith ~/.claude/skills/305-frameworks-spring-boot-modulithSKILL.md
# Spring Boot - Spring Modulith Apply Spring Modulith guidelines for Spring Boot modular monoliths. **What is covered in this Skill?** - Spring Modulith BOM and starter dependency selection - Business-capability package structure for application modules - ApplicationModules verification and architecture tests - Named interfaces and explicit allowed dependencies - Domain events for loose coupling between modules - @ApplicationModuleTest and Scenario-based module integration tests - Generated module documentation, actuator exposure, and observability - Event publication registry choices for reliable domain events **Scope:** Apply recommendations based on the reference rules, official Spring Modulith documentation, and good/bad examples. ## Constraints Before applying Spring Modulith changes, ensure the project compiles. After improvements, run full verification including module structure tests. - **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any change - **PRECONDITION**: The project must be a Spring Boot application; for non-Boot Java modularity use architecture or design skills instead - **BASELINE**: Align dependency choices with Spring Boot 4.0.x and the Spring Modulith compatibility matrix - **SAFETY**: If compilation fails, stop immediately - **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements - **BEFORE APPLYING**: Read the reference for detailed rules, good/bad patterns, and official documentation links ## When to use this skill - Add Spring Modulith to a Spring Boot application - Review Spring Modulith module boundaries - Improve modular monolith architecture in Spring Boot - Add @ApplicationModuleTest tests - Generate Spring Modulith documentation - Refactor Spring Boot modules with Spring Modulith ## Workflow 1. **Read reference and inspect project structure** Read `references/305-frameworks-spring-boot-modulith.md` and inspect the Spring Boot version, Maven dependencies, main application package, and current package/module boundaries. 2. **Model application modules** Identify business-capability modules, public APIs, internal packages, named interfaces, and intentional allowed dependencies. 3. **Apply framework-aligned changes** Add or refine Spring Modulith dependencies, package annotations, architecture verification tests, domain events, and module tests following the reference patterns. 4. **Run verification and report results** Execute appropriate build/tests, especially `ApplicationModules.verify()` and `@ApplicationModuleTest` coverage, then summarize changes, risks, and follow-up module design work. ## Reference For detailed guidance, examples, and constraints, see [references/305-frameworks-spring-boot-modulith.md](references/305-frameworks-spring-boot-modulith.md).
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. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @001-skills-inventory. Part of cursor-rules-java project
Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory. Part of cursor-rules-java project
Use when you need to install the embedded robot agents into either .cursor/agents or .claude/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Copy robot agents. Part of cursor-rules-java project
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of cursor-rules-java project
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic. Part of cursor-rules-java project
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of cursor-rules-java project
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Generate functional requirements in an ADR. Part of cursor-rules-java project