Use 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 Pron
SkillScore50Maintained
Automatic
◆Coding pack
Last verified 8/20/2026
What it changes
Passed 9 of 18 test cases with the skill, and 7 of 18 without it.
Model gemini-3.6-flashMeasured 8/20/2026v111 of 22 cases passed with skill · 18 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
A developer selects functional data structures and modern nullness annotations during Question 1, while declining architecture rules or currency handling. Which reference guide documents should be loaded?
What was checked, without and with the skill
Checked
Without skill
With skill
Loads the JSpecify reference guide for nullness annotations
Refrains from reading unselected dependency reference files
Passed
Passed
case-07 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md97 lines5 files
Add Maven dependencies for improved code quality
Add essential Maven dependencies that enhance code quality, safety, and domain modeling through a consultative, question-driven approach. This is an interactive SKILL.
VAVR: (functional programming with Try/Either and immutable collections)
ArchUnit: (architecture rule enforcement, test scope)
JavaMoney: (Money and Currency API support with JSR 354 and Moneta)
Constraints
Before adding Maven dependencies, ensure the project is in a valid state. Use a consultative, question-driven flow that adds only what the user selects.
MANDATORY: Run ./mvnw validate or mvn validate before any changes
SAFETY: If validation fails, stop and ask the user to fix issues—do not proceed until resolved
BEFORE READING DEPENDENCY REFERENCES: Run the question flow embedded in this SKILL.md first. Ask one consolidated dependency-selection question, then ask only conditional follow-up questions required by the selected options. Read only the dependency references selected by the user's answers. Use consultative language, present trade-offs, and wait for user responses before implementing
When to use this skill
Add Maven dependencies
Add JSpecify nullness dependencies
Add Error Prone NullAway dependencies
Add VAVR functional dependencies
Add ArchUnit architecture testing dependencies
Add JavaMoney dependencies
Workflow
Validate project before changes
Run ./mvnw validate or mvn validate and stop if validation fails.
Ask dependency assessment questions before reading references
Run this XML-included question flow before reading any dependency implementation reference. Ask the consolidated dependency-selection question first, wait for the user's answer, and record selected dependency families before continuing. Ask conditional follow-up questions only when required by the selected dependencies.
Routes Maven version questions to the right workflow by choosing project-local update report interpretation for a user’s own pom.xml, or Maven artifact discovery from maintainer-approved structured evidence. Use when interpreting dependency, plugin, or property update reports; finding Maven coordinates; verifying groupId artifactId version; browsing versions from approved evidence; or constructing artifact URLs without fetching remote content. Part of Plinth Toolkit