marketplace
Review Skills in AI-Unified-Process/marketplace, with license, maintenance context, and source paths.
- Skills
- 13
- Repository stars
- 118
- Identity status
- Source-linked
Provenance
Source and identity
- Profile type
- Repository
- Canonical name
- marketplace
- Public sources
- 1
- License context
- Apache-2.0
Source entries
Agent Skills from marketplace
Repository stars and maintenance signals provide context, but do not automatically become an individual Skill's quality score.
AI-Unified-Process/marketplace
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", "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.
AI-Unified-Process/marketplace
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 Hilla view", "write Hilla tests", "test a React view for Vaadin", "test a @BrowserCallable service", "write Vitest tests for a Hilla app", or mentions Hilla testing, React Testing Library for Vaadin, end
AI-Unified-Process/marketplace
implement
Implements use cases across a Spring Boot + Spring Data JPA backend (flat single-module or hexagonal/ports-and-adapters multi-module) and an Angular frontend wired to that API. Use when the user asks to "implement a use case", "build the API", "create a REST endpoint", "write the data access layer", "build the Angular page/component", or mentions Spring Boot, JPA/Hibernate entities, hexagonal architecture, ports and adapters, or an Angular frontend calling a Java backend.
AI-Unified-Process/marketplace
implement
Implements use cases across a NestJS backend with Drizzle ORM over PostgreSQL and a Next.js App Router frontend wired to that API. Use when the user asks to "implement a use case", "build the API", "create a REST endpoint", "write the data access layer", "build the page", or mentions NestJS modules, controllers, providers, Drizzle queries, repositories, or a Next.js frontend calling a NestJS backend.
AI-Unified-Process/marketplace
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 views, jOOQ queries, Java web app, or database-backed UI. For Hilla (React/TypeScript) views use the implement-hilla skill instead.
AI-Unified-Process/marketplace
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 @BrowserCallable endpoint", or mentions Hilla, client-side Vaadin views, file-based routing, TSX views, or React + jOOQ.
AI-Unified-Process/marketplace
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 testing, Vaadin unit tests, or server-side UI testing.
AI-Unified-Process/marketplace
nest-test
Creates NestJS backend tests with Vitest — unit specs with stubbed repositories, and Supertest end-to-end specs that boot the application against a real PostgreSQL database in Testcontainers. Use when the user asks to "write backend tests", "test the API", "write an e2e test", "test the endpoint", or mentions Supertest, Testcontainers, NestJS testing, or Vitest for a NestJS project.
AI-Unified-Process/marketplace
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. 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 e
AI-Unified-Process/marketplace
playwright-test
Creates Playwright browser-based end-to-end tests for a Next.js frontend running against a live NestJS API, using accessibility-first locators. Use when the user asks to "write Playwright tests", "create e2e tests", "test in the browser", or mentions end-to-end testing, browser tests, or a test case (TC-*) to automate.
AI-Unified-Process/marketplace
reverse-engineer
Reverse-engineers an existing software project into AI Unified Process artifacts: a PlantUML use case diagram, per-use-case specification documents, and an entity model with a Mermaid ER diagram. Use when the user asks to "reverse engineer this codebase", "extract use cases from existing code", "document the system we already have", "generate use case specs from controllers", "derive an entity model from the database", "create AI Unified Process artifacts from a legacy project", or mentions reve
AI-Unified-Process/marketplace
spring-boot-test
Creates Spring Boot tests for REST controllers and Spring Data JPA repositories. Defaults to MockMvcTester and RestTestClient + Testcontainers for new projects (asking the user to confirm on the very first backend test), but detects and follows whichever convention a project already uses — including legacy MockMvc or RestAssured + Testcontainers — rather than migrating it. Use when the user asks to "write backend tests", "test the REST API", "test the controller", "write a Spring Boot test", "te
Pinned paths
Every entry links to a specific source path and commit when available.
Repository context
Activity, license, and repository-level popularity are shown as context.
Open the source
Inspect the public repository