---
title: "aiup-vaadin-jooq"
description: "AI Unified Process for the Vaadin/jOOQ stack, migrations, implementation, tests"
canonical: https://agentpluginsdirectory.com/plugins/aiup-vaadin-jooq
last-updated: 2026-09-25
---

# aiup-vaadin-jooq
AI Unified Process for the Vaadin/jOOQ stack, migrations, implementation, tests
- Slug: aiup-vaadin-jooq
- Publisher: Simon Martinelli
- Repository: https://github.com/AI-Unified-Process/marketplace
- Manifest: aiup-vaadin-jooq/plugin.json
- Version: 2.16.1
- Category (editorial): testing
- Skills: 8 (browserless-test, coverage-check, flyway-migration, hilla-test, implement-hilla, implement, karibu-test, playwright-test)
- MCP servers: 5 (JavaDocs, KaribuTesting, Vaadin, jOOQ, playwright)
- Stars: 132
- Repository created: 2026-02-28
- Repository last pushed: 2026-09-19
- Publisher type: Organization
- Listing: https://agentpluginsdirectory.com/plugins/aiup-vaadin-jooq
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What aiup-vaadin-jooq does, in the publisher's words

aiup-vaadin-jooq is the AI Unified Process construction plugin for applications built with Vaadin or Hilla and jOOQ. It turns the entity model and use case specifications produced by aiup-core into migrations, application code, and tests.

This plugin is designed to continue from the specifications produced by aiup-core. For the complete AI Unified Process workflow, use it alongside aiup-core and select one stack plugin.

Use /implement-hilla instead of /implement for Hilla, followed by /hilla-test for its Vitest frontend tests and Spring Boot backend tests. Since Vaadin 25.1, Browserless Testing is the recommended server-side option for Flow views; /karibu-test remains available for codebases that already use Karibu.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/AI-Unified-Process/marketplace/HEAD/aiup-vaadin-jooq/README.md

## Skills

- browserless-test: Creates Vaadin Browserless server-side unit tests for Vaadin views covering navigation, component interactions, form validation, grid operations, and notifications. Use when the user asks to "write Browserless tests", "write Vaadin UI unit tests", "unit test a Vaadin view without a browser", "creat…
- coverage-check: Audits an already-written use case (UC-XXX) or test case (TC-XXX) against its specification and reports a coverage matrix: which main success scenario steps, alternative flows, business rules, preconditions, and postconditions have code and tests behind them, which are still open, and which code or…
- flyway-migration: Creates versioned Flyway database migration scripts (V*.sql) with sequences, tables, constraints, and foreign keys from the entity model. Use when the user asks to "create a migration", "generate SQL scripts", "set up database tables", "write a Flyway migration", or mentions schema migration, DB mi…
- hilla-test: Creates tests for Hilla use cases on both sides of the browser boundary: Vitest + React Testing Library tests for the React/TypeScript view (with the generated endpoint clients mocked) and Spring Boot integration tests for the @BrowserCallable service behind it. Use when the user asks to "test a Hi…
- implement-hilla: Implements use cases by creating Hilla views, React/TypeScript views with file-based routing calling @BrowserCallable Java services, and jOOQ queries for the data access layer. Use when the user asks to "implement with Hilla", "create a Hilla view", "build a React view for Vaadin", "create a @Bro…
- implement: Implements use cases by creating Vaadin Flow views, forms, and grids, server-side Java UI, and jOOQ queries for the data access layer. Use when the user asks to "implement a use case", "build the UI", "create a Vaadin view", "write the data access layer", or mentions Vaadin Flow, server-side Java…
- karibu-test: Creates Karibu server-side unit tests for Vaadin views covering navigation, component interactions, form validation, grid operations, and notifications. Use when the user asks to "write Karibu tests", "unit test a Vaadin view", "test the UI server-side", "create view tests", or mentions Karibu test…
- playwright-test: Creates Playwright browser-based tests for Vaadin views using the Drama Finder library for type-safe element wrappers with accessibility-first APIs. Covers two test types: integration tests for a single use case (UC-*) and end-to-end journey tests for a test case (TC-*) spanning multiple use cases.…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

## MCP servers

- JavaDocs: transport: streamable-http; url: https://www.javadocs.dev/mcp
- KaribuTesting: transport: streamable-http; url: https://karibu-testing-mcp.martinelli.ch/mcp
- Vaadin: transport: streamable-http; url: https://mcp.vaadin.com/docs
- jOOQ: transport: streamable-http; url: https://jooq-mcp.martinelli.ch/mcp
- playwright: transport: stdio; command: npx @playwright/mcp@latest

Read from the plugin's own mcp.json. Environment variable names only, never values.