aiup-vaadin-jooq

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.

Skills and workflow

Construction
─────────────────────────────────────────────────────────────────────
/flyway-migration  →  /implement  →  /browserless-test  →  /coverage-check
                                  ↘  /playwright-test  (UC-* or TC-*)  ↗

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.

The linked SKILL.md files are the authoritative reference for detailed inputs, outputs, and behavior.

Sub-agent

uc-coverage is the review step of the construction phase. It maps every main success scenario step, alternative flow, business rule, precondition, and postcondition of a specification onto the code and tests that realize it, and reports three things: the gaps, the drift (code or tests the specification no longer describes), and the specification's justified next **Status:** value.

The agent is read-only — it never edits code, tests, or the specification. The implementation and testing skills above call it as their last step, each for its own side. /coverage-check is the front door for calling it yourself — at the end of a construction round, before a review, or mid-way through a large use case with "work in progress" so it lists remaining work instead of defects:

/coverage-check UC-001                 # implementation and tests in one matrix
/coverage-check UC-001 implementation  # narrow the audit to one side
/coverage-check TC-001                 # a journey audits its Flow rows and Validation items

In Claude Code it is available as a sub-agent once the plugin is installed. Hosts without sub-agent support can use agents/uc-coverage.md as an instruction document — its checklist does not depend on Claude Code. The traceability markers it searches for (@UseCase, UC<id>…Test, describe('UC-XXX: …'), @UC-XXX) are the ones the skills above produce.

Installation

Tessl

Initialize the project once:

tessl init --agent agents

agents is the vendor-neutral layout; use claude-code, cursor, gemini, codex, copilot, or copilot-vscode for a specific host. Then install the plugins:

tessl install ai-unified-process/aiup-core
tessl install ai-unified-process/aiup-vaadin-jooq

Depending on the configured agent, skills may be exposed as slash commands or invoked by intent, for example "implement UC-001".

Claude Code

/plugin marketplace add ai-unified-process/marketplace
/plugin install aiup-core
/plugin install aiup-vaadin-jooq

See the marketplace installation guides for other agents and manual adoption.

Prerequisites

• aiup-core and reviewed docs/entity_model.md plus docs/use_cases/UC-*.md artifacts.
• A Maven or Gradle project with Vaadin and jOOQ on the classpath.
• Optional MCP servers configured as described in rules/mcp-servers.md.
• A running application for browser-based Playwright tests.

Inputs and generated artifacts

Migration and implementation skills consume the entity model and individual use case specifications. A /playwright-test TC-XXX journey additionally consumes docs/test_cases/TC-*.md.

The plugin writes Flyway migrations, Vaadin or Hilla implementation classes, server-side tests, and browser tests into the target project's existing Maven or Gradle layout.

Project structure

The common Vaadin Flow layout is:

your-project/
├── docs/
│   ├── entity_model.md
│   ├── use_cases/UC-*.md
│   └── test_cases/TC-*.md
└── src/
    ├── main/
    │   ├── java/                         # /implement
    │   ├── frontend/views/               # /implement-hilla
    │   └── resources/db/migration/       # /flyway-migration
    └── test/
        ├── java/                         # server-side and Playwright tests
        └── resources/db/migration/       # test data seeds

The skills inspect the existing code and build files before choosing packages and paths; the tree above is illustrative, not a required project skeleton.

MCP servers

See rules/mcp-servers.md for optional-server behavior and setup details.

Related documentation

• Getting started
• Workflow and artifacts
• aiup-core

License

Apache-2.0 · © 2025-2026 Simon Martinelli and the AI Unified Process contributors

See LICENSE and NOTICE. "AI Unified Process" identifies the original methodology; derived works must retain the NOTICE file and must not present themselves as the official AI Unified Process.