CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-unified-process/aiup-vaadin-jooq

AI Unified Process plugin for the Vaadin/jOOQ stack

86

1.10x
Quality

91%

Does it follow best practices?

Impact

86%

1.10x

Average score across 13 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

README.md

aiup-vaadin-jooq

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.

What it does

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.

Skills

Each skill is also available as a slash command.

PhaseSkill / commandDescription
Construction/flyway-migrationCreate versioned Flyway migration scripts (V*.sql) from the entity model
Construction/implementImplement use cases as Vaadin Flow views/forms/grids plus jOOQ data access
Construction/implement-hillaImplement use cases as Hilla views (React + @BrowserCallable) plus jOOQ data access
Construction/browserless-testCreate Vaadin Browserless server-side unit tests (recommended)
Construction/karibu-testCreate Karibu server-side unit tests (legacy — superseded since Vaadin 25.1)
Construction/playwright-testCreate Playwright browser-based tests (Drama Finder) — use case integration tests (UC-) or end-to-end test case journeys (TC-)

Workflow

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.

MCP servers

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.

ServerPurpose
VaadinVaadin component APIs, docs, and theming (version-aware)
KaribuTestingKaribu server-side test generation and migration helpers
jOOQjOOQ query DSL reference, code generation, and SQL examples
JavaDocsJavadoc lookup for libraries on the classpath
PlaywrightBrowser automation for end-to-end tests

Installation

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-jooq

Prerequisites

  • ai-unified-process/aiup-core installed, with use case specifications and an entity model already produced under docs/
  • A Maven or Gradle project with Vaadin and jOOQ on the classpath
  • Optional MCP servers (Vaadin, jOOQ, etc.) configured per rules/mcp-servers.md

License

Apache-2.0 · © Simon Martinelli

.mcp.json

README.md

tile.json