AI Unified Process plugin for the Vaadin/jOOQ stack
86
91%
Does it follow best practices?
Impact
86%
1.10xAverage score across 13 eval scenarios
Low
Low-risk findings worth noting
The Vaadin + jOOQ stack plugin for the AI Unified Process (AIUP) — turns use case specifications into implemented, tested Java code.
aiup-vaadin-jooq is the technology-specific layer of the AI Unified Process for applications built with
Vaadin (UI) and jOOQ (data access). It takes the artifacts produced by
ai-unified-process/aiup-core — the entity model and use case specifications — and turns
them into database migrations, Vaadin views, jOOQ queries, and a full test suite.
This plugin covers the Construction phase of the AI Unified Process for the Vaadin/jOOQ stack: schema migrations,
implementation, and testing — with every artifact traceable back to a use case (UC-*).
It is meant to be used together with ai-unified-process/aiup-core, which produces the upstream docs/entity_model.md and
docs/use_cases/UC-*.md artifacts these skills read.
Each skill is also available as a slash command.
| Phase | Skill / command | Description |
|---|---|---|
| Construction | /flyway-migration | Create versioned Flyway migration scripts (V*.sql) from the entity model |
| Construction | /implement | Implement use cases as Vaadin Flow views/forms/grids plus jOOQ data access |
| Construction | /implement-hilla | Implement use cases as Hilla views (React + @BrowserCallable) plus jOOQ data access |
| Construction | /browserless-test | Create Vaadin Browserless server-side unit tests (recommended) |
| Construction | /karibu-test | Create Karibu server-side unit tests (legacy — superseded since Vaadin 25.1) |
| Construction | /playwright-test | Create Playwright browser-based tests (Drama Finder) — use case integration tests (UC-) or end-to-end test case journeys (TC-) |
Construction
────────────────────────────────────────────────────
/flyway-migration → /implement → /browserless-test
↘ /playwright-test (UC-* or TC-*)Use /implement for Vaadin Flow (server-side Java) views and /implement-hilla for Hilla
(React/TypeScript) views — both share the same jOOQ data access conventions.
These skills read the AI Unified Process artifacts under docs/ (docs/entity_model.md, docs/use_cases/UC-*.md, and
docs/test_cases/TC-*.md) produced by ai-unified-process/aiup-core and write code and tests into your Maven/Gradle project.
The plugin wires up MCP servers that give the skills authoritative, version-correct knowledge of the stack. Some are
optional — see rules/mcp-servers.md for setup details.
| Server | Purpose |
|---|---|
| Vaadin | Vaadin component APIs, docs, and theming (version-aware) |
| KaribuTesting | Karibu server-side test generation and migration helpers |
| jOOQ | jOOQ query DSL reference, code generation, and SQL examples |
| JavaDocs | Javadoc lookup for libraries on the classpath |
| Playwright | Browser automation for end-to-end tests |
Install from the Tessl registry (install the core plugin too, if you haven't already):
tessl install ai-unified-process/aiup-core
tessl install ai-unified-process/aiup-vaadin-jooqai-unified-process/aiup-core installed, with use case specifications and an entity
model already produced under docs/rules/mcp-servers.mdApache-2.0 · © Simon Martinelli