setup-agentic-scaffoldinglisted

# Setup Agentic Scaffolding # Version: 0.13.1 ## 1. When to use this skill Run this skill **once per machine** and **revisit once per project** to configure the prerequisites for the Quarkus + LangChain4j agentic stack — before scaffolding or auditing any project. It is the entry point of the flow: - **Phase A — toolchain (machine-level):** JDK 25+/GraalVM, JBang, a container runtime, Maven or the Quarkus CLI. - **Phase B — MCP registration (per agent):** the **Quarkus Agents MCP** and **context7**, wired through the mechanism of whichever agent is running. - **Phase C — conventions (project-level):** the always-on conventions file (`CLAUDE.md` or `AGENTS.md`) copied into the user's project root. This skill is **user-invoked only** (`disable-model-invocation: true`); it never triggers itself from a task description. ## 2. Bootstrap license (read first) The project conventions (`CLAUDE.md` / `AGENTS.md` §1) make the Quarkus Agents MCP mandatory for every Quarkus task and tell the agent to **stop** if required tooling is missing. **That rule does not apply to this skill.** Installing that tooling is precisely this skill's job, so it legitimately operates **before and without** the Quarkus Agents MCP and context7. Do not stop or defer to the MCP here — proceed with Phases A–C and register the MCP as part of the work. ## 3. How this skill works (process) Every phase follows the same house pattern — never act blind, never clobber: 1. **Explore.** Detect current stat