Name: 111 Java Maven Dependencies
Author: jabrena

111 Java Maven Dependencies

Use when you need to add or evaluate Maven dependencies that improve code quality — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), or architecture testing (ArchUnit) — and want a consultative, question-driven approach that adds only what you actually need. Part of the skills-for-java project

jabrena356 starsApr 9, 2026

Occupation
Categories: Full Stack

Add essential Maven dependencies that enhance code quality and safety through a consultative, question-driven approach. This is an interactive SKILL.

What is covered in this Skill?

JSpecify: (nullness annotations, provided scope)
Error Prone + NullAway: (enhanced static analysis with compile-time null checking)
VAVR: (functional programming with Try/Either and immutable collections)
ArchUnit: (architecture rule enforcement, test scope)

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 ASKING QUESTIONS: Read the reference to use the exact wording and options from the template. Ask questions one-by-one in strict order (JSpecify → Enhanced Compiler Analysis (conditional) → VAVR → ArchUnit) and add only what the user selects. Use consultative language, present trade-offs, and wait for user responses before implementing

Add essential Maven dependencies that enhance code quality and safety through a consultative, question-driven approach. This is an interactive SKILL.

What is covered in this Skill?

JSpecify: (nullness annotations, provided scope)
Error Prone + NullAway: (enhanced static analysis with compile-time null checking)
VAVR: (functional programming with Try/Either and immutable collections)
ArchUnit: (architecture rule enforcement, test scope)

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 ASKING QUESTIONS: Read the reference to use the exact wording and options from the template. Ask questions one-by-one in strict order (JSpecify → Enhanced Compiler Analysis (conditional) → VAVR → ArchUnit) and add only what the user selects. Use consultative language, present trade-offs, and wait for user responses before implementing

111 Java Maven Dependencies

Constraints

111 Java Maven Dependencies

Constraints

When to use this skill

Reference

microsoft-vscode-extensions-copilot-assets-prompts-skills-project-setup-info-context7-skill-md

How to setup a project

Coding Standards

Nuxt4 Patterns

Coding Standards

Nextjs Turbopack