eldermoraes/quarkus-agentic-scaffolding / skills/scaffold-project
scaffold-project
VerifiedScaffold Quarkus + LangChain4j projects end-to-end and add agentic components to existing ones — AI services, tools, agents and multi-agent workflows, RAG pipelines, MCP clients and servers (Model Context Protocol), guardrails, and embedding store setups. Use this whenever the user wants a new Quarkus + LangChain4j project or module created, or an agentic component added to an existing project in this stack, including a baseline pom.xml, application.properties, project layout, or starter classes.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 20.9 KB |
| agents/openai.yaml | config | 669 B |
| templates/Agent.java.template | other | 28.4 KB |
| templates/AiService.java.template | other | 6.1 KB |
| templates/AiServiceTest.java.template | other | 6.2 KB |
| templates/ApplicationIT.java.template | other | 2.7 KB |
| templates/Guardrails.java.template | other | 4.5 KB |
| templates/McpClient.java.template | other | 2.5 KB |
| templates/McpServer.java.template | other | 2.6 KB |
| templates/RagSetup.java.template | other | 9.1 KB |
| templates/RestResource.java.template | other | 3.1 KB |
| templates/Tools.java.template | other | 2.3 KB |
| templates/application.properties.template | other | 12.6 KB |
| templates/pom.xml.template | other | 7.6 KB |
templates/Tools.java.template
View on GitHubpackage org.acme.tools;
import dev.langchain4j.agent.tool.Tool;
import io.smallrye.common.annotation.RunOnVirtualThread;
import jakarta.enterprise.context.ApplicationScoped;
/*
* Function-calling tools — a CDI bean whose @Tool methods the model may invoke to fetch data
* or take actions. Replace the triage-domain example below with your own methods.
*
* Wiring (two equivalent ways):
* - globally, for every method of an AI service: @RegisterAiService(tools = TicketTools.class)
* - per AI-service method: @ToolBox(TicketTools.class)
*
* Exposure: this dev.langchain4j @Tool reaches only the AI services wired to it. An MCP server
* in the same application (mcp-server-http or mcp-server-stdio) would also publish it to
* every MCP client unless quarkus.mcp.server.support-langchain4j-annotations=false: the
* properties baseline carries that line, commented, in its MCP server block, to uncomment
* with the block. To offer one of these methods over MCP, add an MCP @Tool that delegates to
* it (McpServer.java.template).
*
* Blocking: tools run blocking by default. Annotate a method to change that —
* @Blocking (caller thread), @NonBlocking (event loop; for Uni/CompletionStage returns), or
* @RunOnVirtualThread for blocking I/O (DB/REST) so it stays off the event loop
* (project conventions section 2).
*
* Tool-level guardrails: validate a tool's arguments/results with @ToolInputGuardrails /
* @ToolOutputGuardrails — see Guardrails.java.template for the guardrail beans they reference.
*/
@ApplicationScoped
public class TicketTools {
/** A small typed result — the model receives structured, unambiguous tool output. */
public record CustomerContext(String plan, int openTickets) {}
@Tool("Looks up the customer's plan and open-ticket count")
@RunOnVirtualThread // a real lookup hits a DB or REST client — keep that blocking I/O off the event loop
public CustomerContext lookupCustomer(String customerId) {
// Deterministic fake. Replace with a Panache repository or a REST client call.
int openTickets = Math.floorMod(customerId.hashCode(), 5);
String plan = openTickets > 2 ? "ENTERPRISE" : "STANDARD";
return new CustomerContext(plan, openTickets);
}
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |