BootUI — скилл

---
name: bootui
description: Install, configure, and use BootUI in Spring Boot and Quarkus applications; assess a running application, propose a prioritized action plan, and execute only approved fixes using runtime evidence. Use when asked to add or troubleshoot BootUI, assess application health, or investigate a slow or failing endpoint, exceptions, SQL, Hibernate, beans, mappings, configuration, health, metrics, logs, or traces; to find runtime-only bugs such as N+1 queries, split transactions, or bypassed @Transactional proxies, or check which routes a code change affects and verify what it changed at runtime after the tests; also for architecture, security, memory, database, REST, pentest, GraalVM, CRaC, or vulnerability scans, or connecting an AI agent to BootUI.
license: Apache-2.0
---

# BootUI

Use BootUI as a local, runtime-grounded source of information for Spring Boot and Quarkus applications. Keep it
local-only, preserve its fail-closed defaults, and make the smallest application change that addresses the user's request.

## Establish the application context

Before changing anything:

1. Identify the build tool and use its wrapper when present.
2. Identify the framework and web stack:
   - Spring Boot servlet
   - Spring Boot WebFlux
   - Quarkus
3. Confirm Java 17 or later and a supported framework version (Spring Boot 4.x or Quarkus 3.x).
4. Find the runnable module, active development profile, configured HTTP port, and existing BootUI dependency.
5. Run the project's existing focused tests before and after changes when practical.

Keep an existing application's own web stack. BootUI adds no web starter; a non-web Spring application needs an
explicitly approved servlet starter and embedded server to serve the console. `bootui.force-web` requests servlet
mode, not dependencies. Do not add the Spring starter to Quarkus or the Quarkus extension to Spring.

## Install BootUI

Add the dependency only when the user asked for BootUI or approves the change. If a diagnostic request arrives and
BootUI is not on the classpath, say so first rather than installing it silently.

Determine the latest stable BootUI version from Maven Central or the
[BootUI releases](https://github.com/jdubois/boot-ui/releases); do not guess a version or use a snapshot unless requested.
Use the project's existing dependency-management and formatting conventions.

Choose exactly one dependency:

| Application | Maven coordinates |
| --- | --- |
| Spring Boot (Spring MVC or WebFlux) | `com.julien-dubois.bootui:bootui-spring-boot-starter` |
| Quarkus | `com.julien-dubois.bootui:bootui-quarkus` |

The Spring starter brings no web stack: keep the application's own `spring-boot-starter-web` or