Why does this skill mandate constructor injection?

Constructor injection is required because it promotes immutability, enables easier unit testing with mocks, and prevents the creation of objects in an invalid, partially-injected state.

How does the skill handle null values in dependency injection?

The skill enforces the use of @Dependent scope for producers that return null and recommends the Instance pattern for resolving optional dependencies safely.

Is this skill compatible with Quarkus?

Yes, while it follows core Jakarta CDI standards, it includes specific support for MicroProfile Config and Quarkus-specific injection patterns.

When should I use @ApplicationScoped versus @Singleton?

The skill generally recommends @ApplicationScoped for stateless business logic to leverage CDI's proxying capabilities, suggesting @Singleton only for specific eager-initialization needs.

Java CDI Standards

Name: Java CDI Standards
Author: cuioss

bycuioss

Desarrollo de API

Enforces Jakarta Contexts and Dependency Injection (CDI) standards using constructor injection, scope management, and robust producer patterns.

Acerca de

This skill provides Claude Code with deep expertise in Jakarta CDI patterns, ensuring consistent and reliable dependency management in Java applications. It focuses on modern best practices such as mandatory constructor injection for enhanced testability, precise lifecycle scope selection, and strict rules for producer methods to prevent common runtime exceptions. Designed for Jakarta EE and Quarkus environments, it helps developers build decoupled, maintainable, and type-safe backend architectures by automating the application of enterprise-grade injection standards.

Características Principales

Manages optional dependencies using Instance<T> resolution patterns
Provides automated troubleshooting for Unsatisfied and Ambiguous resolutions
Standardizes CDI scope selection including Application, Request, and Dependent scopes
Enforces mandatory constructor injection for immutability and testability
0 GitHub stars
Guides the safe implementation of producer methods and null-handling rules

Casos de Uso

Architecting complex dependency graphs with producers and optional services
Refactoring legacy field-injected Java beans to modern constructor-based CDI
Developing scalable backend services for Jakarta EE or Quarkus applications

Acerca de

Características Principales

Manages optional dependencies using Instance<T> resolution patterns
Provides automated troubleshooting for Unsatisfied and Ambiguous resolutions
Standardizes CDI scope selection including Application, Request, and Dependent scopes
Enforces mandatory constructor injection for immutability and testability
0 GitHub stars
Guides the safe implementation of producer methods and null-handling rules

Casos de Uso

Architecting complex dependency graphs with producers and optional services
Refactoring legacy field-injected Java beans to modern constructor-based CDI
Developing scalable backend services for Jakarta EE or Quarkus applications