401-frameworks-quarkus-core
This Claude Code skill provides guidance for building and reviewing Quarkus applications, covering CDI bean management, scoping, configuration profiles, lifecycle handlers, interceptors, events, and virtual thread support. Use it when refactoring Quarkus application structure, applying CDI best practices, implementing cross-cutting concerns through interceptors and events, configuring beans and profiles, or optimizing for native image compilation and Java 21 virtual threads.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/401-frameworks-quarkus-core && cp -r /tmp/401-frameworks-quarkus-core/skills/401-frameworks-quarkus-core ~/.claude/skills/401-frameworks-quarkus-coreSKILL.md
# Quarkus Core Guidelines Apply Quarkus core guidelines for CDI beans, configuration, profiles, and lifecycle. **What is covered in this Skill?** - @QuarkusMain and application entry (when custom main is needed) - CDI scopes: @ApplicationScoped, @Singleton, @Dependent; bean disambiguation (@Default, @Alternative, @Named) - Constructor injection with @Inject - CDI interceptors (@Interceptor, @InterceptorBinding) for cross-cutting concerns - CDI events: @Observes StartupEvent / ShutdownEvent, @ObservesAsync for async dispatch - Programmatic injection with Instance<T> for dynamic bean selection - @ConfigMapping and structured configuration with Bean Validation (@Valid) - Profile-specific properties (%dev, %test, %prod) and @IfBuildProfile - Startup and shutdown observers (@Startup, @PreDestroy) - Virtual threads with @RunOnVirtualThread (Java 21+) - Native-image safety: @RegisterForReflection, @DisabledOnNativeImage **Scope:** Apply recommendations based on the reference rules and good/bad code examples. ## Constraints Before applying any Quarkus changes, ensure the project compiles. If compilation fails, stop immediately. After applying improvements, run full verification. - **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any change - **PREREQUISITE**: Project must compile successfully before applying Quarkus core improvements - **SAFETY**: If compilation fails, stop immediately — compilation failure is a blocking condition - **BLOCKING CONDITION**: Compilation errors must be resolved by the user before proceeding - **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements - **BEFORE APPLYING**: Read the reference for detailed rules, good/bad patterns, and constraints ## When to use this skill - Review Java code for Quarkus application structure and CDI - Apply best practices for Quarkus configuration and beans - Improve CDI interceptors, events, or programmatic injection in Quarkus - Add virtual-thread configuration or tune CDI lifecycle ## Workflow 1. **Read reference and assess project context** Read `references/401-frameworks-quarkus-core.md` and inspect the current project setup before proposing changes. 2. **Gather scope and decide target improvements** Identify requested outcomes, constraints, and the minimum safe set of changes to apply. 3. **Apply framework-aligned changes** Implement or refactor configuration/code following the reference patterns and project conventions. 4. **Run verification and report results** Execute appropriate build/tests and summarize what changed, what was verified, and any follow-up actions. ## Reference For detailed guidance, examples, and constraints, see [references/401-frameworks-quarkus-core.md](references/401-frameworks-quarkus-core.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