aiup-vaadin-jooq
v2.12.1AI Unified Process plugin for the Vaadin/jOOQ stack
By Simon Martinelli111 GitHub starsUpdated last month
Directory evidence
- Runtimes
- Claude Code and Agent Plugins
- Parsed components
- 11 skill or MCP entries
- Source updated
- Aug 10, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install aiup-vaadin-jooq for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install aiup-vaadin-jooq@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/AI-Unified-Process/marketplaceClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is aiup-vaadin-jooq/.
Plugin files
├── .claude-plugin/plugin.json├── plugin.json├── skills/browserless-test/SKILL.md├── skills/flyway-migration/SKILL.md├── skills/implement/SKILL.md├── skills/implement-hilla/SKILL.md├── skills/karibu-test/SKILL.md├── skills/playwright-test/SKILL.md└── .mcp.json
Included Skills6
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", "create view tests with the official Vaadin testing framework", or mentions Browserless testing, SpringBrowserlessTest, browserless-test-junit6, UI Unit Testing, or server-side Vaadin testing.
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 migration, database versioning, or SQL migration files.
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 views, jOOQ queries, Java web app, or database-backed UI. For Hilla (React/TypeScript) views use the implement-hilla skill instead.
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 @BrowserCallable endpoint", or mentions Hilla, client-side Vaadin views, file-based routing, TSX views, or React + jOOQ.
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 testing, Vaadin unit tests, or server-side UI testing.
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. Use when the user asks to "write Playwright tests", "create e2e tests", "write integration tests", "test in the browser", "write IT tests", "automate a test case", "test a user journey", or mentions end-to-end testing, browser tests, UI integration tests, Playwright for Vaadin, or Drama Finder. Also trigger when the user references a use case (UC-*) or a test case (TC-*) and asks for Playwright or E2E tests.
MCP servers5
- url
- https://www.javadocs.dev/mcp
- url
- https://karibu-testing-mcp.martinelli.ch/mcp
- url
- https://mcp.vaadin.com/docs
- url
- https://jooq-mcp.martinelli.ch/mcp
- command
- npx
- args
- @playwright/mcp@latest
Plugin manifests2
{
"name": "aiup-vaadin-jooq",
"description": "AI Unified Process plugin for the Vaadin/jOOQ stack",
"version": "2.12.1",
"author": {
"name": "Simon Martinelli",
"email": "[email protected]",
"url": "https://unifiedprocess.ai"
}
}{
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
"name": "aiup-vaadin-jooq",
"version": "2.12.1",
"description": "AI Unified Process plugin for the Vaadin/jOOQ stack",
"author": {
"name": "Simon Martinelli",
"email": "[email protected]",
"url": "https://unifiedprocess.ai"
},
"homepage": "https://unifiedprocess.ai",
"repository": "https://github.com/AI-Unified-Process/marketplace"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[aiup-vaadin-jooq on Agent Plugins Marketplace](https://pluginsmp.com/plugins/aiup-vaadin-jooq)