本文へ移動
cccskills
無料GitHub で公開

401-frameworks-quarkus-core

Use when building or reviewing core Quarkus applications with CDI beans and scopes, SmallRye Config and profiles, lifecycle, interceptors and events, virtual threads, and test-friendly design. This should trigger for requests such as 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. ; Review Quarkus CDI bean lifecycle and configuration. Part of Plinth Toolkit

インストール方法を見る

含まれるファイル(2)

  • SKILL.md3.5 KB
  • references/401-frameworks-quarkus-core.md25.8 KB

SKILL.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
  • Review Quarkus CDI bean lifecycle and configuration

Workflow

  1. Read reference and assess project context

Read references/401-frameworks-quarkus-core.md and inspect the current project setup before proposing changes.

  1. Gather scope and decide target improvements

Identify requested outcomes, constraints, and the minimum safe set of changes to apply.

  1. Apply framework-aligned changes

Implement or refactor configuration/code following the reference patterns and project conventions.

  1. 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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the project root. This should trigger for requests such as Create embedded commands inventory checklist; Generate INVENTORY-COMMANDS-JAVA.md; Use @001-commands-inventory; Inventory embedded Java project commands; List command files bundled for Java agents. Part of Plinth Toolkit

日本語の概要は準備中です。原文の説明を表示しています。

jabrena/plinth4482026年10月8日 更新

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; Inventory embedded Java agent definitions; List generated agent roles for Java development. Part of Plinth Toolkit

日本語の概要は準備中です。原文の説明を表示しています。

jabrena/plinth4482026年10月8日 更新

Use when you need to generate a checklist document with Java system prompts from skills.xml, following the embedded section template and producing INVENTORY-SKILLS-JAVA.md. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @003-skills-inventory; Inventory Java cursor rule skills; List available Java system prompt skills. Part of Plinth Toolkit

日本語の概要は準備中です。原文の説明を表示しています。

jabrena/plinth4482026年10月8日 更新

Use when you need to install the embedded project commands into command directories (.github/commands, .claude/commands, .cursor/command, .codex/commands), selecting the destination interactively and copying the embedded command definitions from project assets. This should trigger for requests such as Install embedded commands; Bootstrap .cursor/command; Bootstrap .claude/commands; Copy project commands; Install project command suite. Part of Plinth Toolkit

日本語の概要は準備中です。原文の説明を表示しています。

jabrena/plinth4482026年10月8日 更新

Use when you need to install the embedded robot agents into .github/agents, .claude/agents, .cursor/agents, or .codex/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 .github/agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Bootstrap .codex/agents; Copy robot agents. Part of Plinth Toolkit

日本語の概要は準備中です。原文の説明を表示しています。

jabrena/plinth4482026年10月8日 更新

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 Plinth Toolkit

日本語の概要は準備中です。原文の説明を表示しています。

jabrena/plinth4482026年10月8日 更新

jabrena のスキルをすべて見る

このスキルの問題を報告する