--- title: "aiup-vaadin" description: "AI Unified Process UI layer with Vaadin, Flow and Hilla views, Browserless and Vitest view tests, and Playwright end-to-end tests" canonical: https://agentpluginsdirectory.com/plugins/aiup-vaadin last-updated: 2026-10-24 --- # aiup-vaadin AI Unified Process UI layer with Vaadin, Flow and Hilla views, Browserless and Vitest view tests, and Playwright end-to-end tests - Slug: aiup-vaadin - Publisher: Simon Martinelli - Repository: https://github.com/AI-Unified-Process/marketplace - Manifest: aiup-vaadin/plugin.json - Version: 3.0.1 - Category (editorial): other - Skills: 5 (hilla-ui-test, hilla-ui, vaadin-e2e-test, vaadin-flow-ui-test, vaadin-flow-ui) - MCP servers: 2 (Vaadin, playwright) - Stars: 150 - Repository created: 2026-02-28 - Repository last pushed: 2026-10-24 - Publisher type: Organization - Listing: https://agentpluginsdirectory.com/plugins/aiup-vaadin - Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json ## What aiup-vaadin does, in the publisher's words aiup-vaadin is the AI Unified Process layer plugin for the UI and E2E layers of a Vaadin application. It builds and tests the views of a use case, server-side Java views with Vaadin Flow, or React views with Hilla, on top of the service layer, and automates use cases and test case journeys in the browser with Playwright and Drama Finder. It is one plugin of a layered setup: a project combines aiup-core with one plugin per layer. The skills are driven by aiup-core and need aiup-core 3.0.0 or later: - /stack records in docs/architecture/stack.md which skill builds and tests each layer - /use-case-implement UC-XXX runs the implementation skills bottom-up and hands each layer the Handover of the one below From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/AI-Unified-Process/marketplace/HEAD/aiup-vaadin/README.md ## Skills - hilla-ui-test: Writes the UI layer tests of a use case (UC-XXX) for Hilla React views with Vitest in browser mode and React Testing Library, with the generated endpoint clients mocked by vi.spyOn: no server, no database. Covers what the actor sees: rendering, form input and useForm validation, the calls the view… - hilla-ui: Implements the UI layer of a use case (UC-XXX) with Hilla: a @BrowserCallable endpoint that delegates to the service layer, and a React/TypeScript view under src/main/frontend/views/ with file-based routing, Vaadin React components, useForm validation from the generated models, and the messages the… - vaadin-e2e-test: Writes the end-to-end tests of a Vaadin application (Flow or Hilla) with Playwright for Java and the Drama Finder library's type-safe, accessibility-first element wrappers, against the running application. Two kinds: a use case test (UC-XXX), one class UCIT with @Nested groups per alterna… - vaadin-flow-ui-test: Writes the UI layer tests of a use case (UC-XXX) for Vaadin Flow views with Vaadin Browserless Testing, the official server-side framework that runs the view inside the JVM without a browser, covering navigation, form input and Binder validation, grid contents, dialogs, confirmations, and the notif… - vaadin-flow-ui: Implements the UI layer of a use case (UC-XXX) as server-side Java with Vaadin Flow: @Route views inside the application layout, Grids with lazy data providers that call the service layer, forms with Binder and Bean Validation, dialogs and ConfirmDialogs, notifications with the messages the specifi… Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized. ## MCP servers - Vaadin: transport: streamable-http; url: https://mcp.vaadin.com/docs - playwright: transport: stdio; command: npx @playwright/mcp@latest Read from the plugin's own mcp.json. Environment variable names only, never values.