vaadin-usage-review
Vaadin Usage Review
Overview
Audits Vaadin code for places where a custom workaround or hack was used even though an official Vaadin API exists — typically because whoever wrote it (often an AI agent) didn't look it up.
This includes component choice: raw HTML elements (Div, Span, native <input>/<button>, flexbox Divs) or custom-styled markup used where an equivalent Vaadin component already exists (TextField, Button, VerticalLayout/HorizontalLayout, Badge, Card, …). Vaadin components are the default; raw HTML is the exception that must earn its place — see Component choice.
This skill is report-only. It NEVER edits, fixes, or stages files. It produces a findings report.
The Vaadin MCP server is the single source of truth. Every claim that "an official API exists" MUST be verified against the Vaadin MCP and cited. Do not assert official APIs from memory.
The Two Iron Rules
- The MCP is the single source of truth. If the Vaadin MCP is unavailable, STOP and report that — do not fall back to memory, training knowledge, or the web. A guess is worse than an honest "cannot verify".
- Report only. No file edits, no fixes applied, no commits. Findings describe the official alternative; they do not change code.