jabrena/plinth / skills/111-java-maven-dependencies
111-java-maven-dependencies
VerifiedUse when you need to add or evaluate Maven dependencies that improve code quality or domain modeling — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), architecture testing (ArchUnit), or money and currency support (JavaMoney) — and want a consultative, question-driven approach that adds only what you actually need. This should trigger for requests such as Add Maven dependencies; Add JSpecify nullness dependencies; Add Error Prone NullAway dependencies; Add VAVR functional dependencies; Add ArchUnit architecture testing dependencies; Add JavaMoney dependencies. Part of Plinth Toolkit
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.9 KB |
| references/111-java-maven-dependencies-archunit.md | markdown | 1.3 KB |
| references/111-java-maven-dependencies-javamoney.md | markdown | 2.8 KB |
| references/111-java-maven-dependencies-jspecify.md | markdown | 4.0 KB |
| references/111-java-maven-dependencies-vavr.md | markdown | 1.2 KB |
references/111-java-maven-dependencies-vavr.md
View on GitHub---
name: 111-java-maven-dependencies-vavr
description: VAVR Maven dependency guidance for the interactive Maven dependencies skill.
license: Apache-2.0
metadata:
author: Juan Antonio Breña Moral
version: 0.19.0
---
# Add Maven dependencies for improved code quality
## Role
You are a Senior software engineer with extensive experience in Java software development.
## Goal
Add VAVR only when the user selects functional programming support in the SKILL.md question flow.
## Constraints
VAVR is an application dependency. Add it only when selected and preserve the existing POM structure.
- Use default Maven compile scope for VAVR.
- Do not add VAVR when the user skipped functional programming support.
## Steps
### Step 1: Add selected version property
```xml
<vavr.version>0.10.6</vavr.version>
```
### Step 2: Add VAVR dependency
```xml
<dependency>
<groupId>io.vavr</groupId>
<artifactId>vavr</artifactId>
<version>${vavr.version}</version>
</dependency>
```
### Step 3: Report common usage
Mention VAVR is useful for `Try`, `Either`, and immutable collections. Recommend adding examples only if the user asks or if the change introduces VAVR into existing code.Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |