marketplace

Implements the UI layer of a use case (UC-XXX) as an Angular client: standalone page and presentational components, signal() state, one hand-written HttpClient service per entity with TypeScript models that match the API layer's DTOs field by field, and routes in app.routes.ts. Consumes the Handover of the API layer (endpoints, DTOs) and checks the JSON contract against it. Use when the user asks to "build the Angular page", "implement the UI of UC-001", "create the Angular component", "wire the frontend to the REST API", or mentions Angular, standalone components, signals, or an Angular client calling a backend. Normally run by /use-case-implement as the UI layer of a project whose docs/architecture/stack.md names Angular; it can also be run directly. Does not write tests — that is /angular-ui-test.

Implements the UI layer of a use case (UC-XXX) as an Angular client: standalone page and presentational components, signal() state, one hand-written HttpClient service per entity with TypeScript models that match the API layer's DTOs field by field, and routes in app.routes.ts. Consumes the Handover of the API layer (endpoints, DTOs) and checks the JSON contract against it. Use when the user asks to "build the Angular page", "implement the UI of UC-001", "create the Angular component", "wire the frontend to the REST API", or mentions Angular, standalone components, signals, or an Angular client calling a backend. Normally run by /use-case-implement as the UI layer of a project whose docs/architecture/stack.md names Angular; it can also be run directly. Does not write tests — that is /angular-ui-test.

Writes the UI-layer tests of a use case (UC-XXX) for an Angular client with Vitest and Angular's own testing idioms: TestBed component tests for the routed page, HttpTestingController for the API boundary, DI overrides for non-HTTP services, and plain service tests — in UC-XXX-<slug>.spec.ts files with a describe('UC-XXX: …') block. Use when the user asks to "write frontend tests", "test the Angular component", "write a Vitest test", "unit test an Angular page", "test the UI of UC-001", or mentions TestBed, ComponentFixture, or HttpTestingController. Normally run by /use-case-test as the UI test layer of a project whose docs/architecture/stack.md names Angular; it can also be run directly. Browser tests against the running application are /playwright-e2e-test.

Writes the UI-layer tests of a use case (UC-XXX) for an Angular client with Vitest and Angular's own testing idioms: TestBed component tests for the routed page, HttpTestingController for the API boundary, DI overrides for non-HTTP services, and plain service tests — in UC-XXX-<slug>.spec.ts files with a describe('UC-XXX: …') block. Use when the user asks to "write frontend tests", "test the Angular component", "write a Vitest test", "unit test an Angular page", "test the UI of UC-001", or mentions TestBed, ComponentFixture, or HttpTestingController. Normally run by /use-case-test as the UI test layer of a project whose docs/architecture/stack.md names Angular; it can also be run directly. Browser tests against the running application are /playwright-e2e-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.

Generates bUnit component tests for Blazor components (.razor): renders the page, fills and submits its forms, asserts the rendered markup and the validation and error messages the use case states, and replaces the handlers and services it injects with test doubles, one test per scenario and business rule tagged with [UseCase]. Use when the user asks to "write bUnit tests", "test a Blazor component", "test the Razor page of UC-001", "create UI tests for Blazor", or mentions bUnit or xUnit rendering tests. Backend tests are /dotnet-test, browser tests /playwright-test.

Creates or updates BPMN 2.0 business process models (docs/processes/BP-XXX-*.bpmn) from the requirements catalog and the use case diagram: one pool per process, one lane per actor, every activity one use case, gateways for the decisions between them, and a diagram layout a modeler such as bpmn.io can open. Every process gets a BP-XXX id for communication and traceability; run it with that id (e.g. /business-process BP-001) to update one process. Use when the user asks to "model the business process", "create a BPMN", "draw the process", "connect the use cases into a process", "update BP-001", or mentions a business process, process model, BPMN, swimlanes, or a .bpmn file. Also trigger when a review or the use case skills report a summary use case whose parts hand over to another role, wait for an event or deadline, or run in parallel — that flow is a business process. The resulting model is what /test-case BP-XXX derives end-to-end test cases from.

Audits an already-written use case (UC-XXX) or test case (TC-XXX) against its specification and reports a coverage matrix: which main success scenario steps, alternative flows, business rules, preconditions, and postconditions have code and tests behind them, which are still open, and which code or tests have drifted away from the specification. Use when the user asks to "check coverage", "run a coverage check", "is UC-001 fully implemented", "is UC-001 completely tested", "audit the use case", "show me the coverage matrix", "do a traceability check", "what is still missing for UC-001", or "can I set the status to Tested". This is specification coverage, not line coverage from a coverage report. It reports only — it writes no code, no tests, and no files. When the user wants the gaps closed rather than listed, use /implement, /implement-hilla, /browserless-test, /hilla-test, /karibu-test, or /playwright-test instead.

Audits an already-written use case (UC-XXX) or test case (TC-XXX) against its specification and reports a coverage matrix: which main success scenario steps, alternative flows, business rules, preconditions, and postconditions have code and tests behind them, which are still open, and which code or tests have drifted away from the specification. Use when the user asks to "check coverage", "run a coverage check", "is UC-001 fully implemented", "is UC-001 completely tested", "audit the use case", "show me the coverage matrix", "do a traceability check", "what is still missing for UC-001", or "can I set the status to Tested". This is specification coverage, not line coverage from a coverage report. It reports only — it writes no code, no tests, and no files. When the user wants the gaps closed rather than listed, use /implement, /spring-boot-test, /vitest-test, or /playwright-test instead.

Generates C# backend unit and integration tests for EF Core DbContext repositories, domain services, and vertical slice handlers using xUnit or NUnit against SQLite in-memory or Testcontainers databases, one test per scenario and business rule, each tagged with [UseCase]. Use when the user asks to "write backend tests for C#", "write .NET tests for this handler", "test ef core context", "write integration tests for dotnet", or mentions xUnit or NUnit handler tests. Blazor component tests are /bunit-test, browser tests /playwright-test.

Creates Drizzle ORM schema definitions and generated SQL migrations for PostgreSQL from the entity model. Use when the user asks to "create a migration", "generate SQL", "set up database tables", "update the schema", or mentions Drizzle, drizzle-kit, pg-core, schema.ts, or database versioning for a NestJS project.

Builds the data layer of a C# / .NET project from docs/entity_model.md with Entity Framework Core: generates the entity classes, writes IEntityTypeConfiguration Fluent API mappings (table names, decimal precision, enum conversions, foreign keys, unique indexes, binary columns), registers them in the DbContext, and adds a native C# migration with dotnet ef migrations add. Use when the user asks to "create an EF Core migration", "add ef migration", "update the schema with ef core", "map the entities in the DbContext", "generate a db migration for .net", or mentions EF Core, DbContext, Fluent API, or dotnet ef in a Blazor .NET project.

Creates entity model documents with Mermaid.js ER diagrams and attribute tables defining entities, relationships, data types, and validation rules. Use when the user asks to "create an entity model", "design a data model", "draw an ERD", "define database schema", "model entities", or mentions entity-relationship diagram, ER diagram, database design, or data modeling. Also trigger whenever the task is to produce, write, or design an entity model or data model document (e.g. docs/entity_model.md) from a requirements catalog — including phrasings like "data model design", "the team needs an entity model before development", or a request to document entities with attributes, data types, precision, and validation or cross-attribute constraints.

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.

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.

Builds the migration layer of a use case (UC-XXX) with Flyway: versioned V*.sql scripts with sequences, tables, snake_case columns, CHECK and UNIQUE constraints, and foreign keys from the entity model, placed in the migration location docs/architecture/stack.md records, and only the tables, columns, and constraints the use case needs that the schema does not have yet. Marks a constraint that enforces a business rule with -- UC-XXX BR-YYY. Normally run by /use-case-implement as the first layer; can be run directly, with a use case or for the whole entity model. Use when the user asks to "create a migration", "write a Flyway migration", "add a column", "create the tables for UC-001", "set up the database schema", or mentions Flyway, schema migration, DB migration, database versioning, or SQL migration files in a project that combines layer plugins. Test data migrations belong to the test skills.

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, endpoint mocking, or testing TSX views.

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

Implements use cases for C# and Blazor (.NET 10) applications using a Vertical Slice Architecture. Takes a UC-XXX.md specification and generates feature-folder components, C# Commands/Queries with their handlers and validators, EF Core entities/configurations, and Blazor (Razor) pages/components, with UC-XXX BR-YYY markers on every business rule. Use when the user asks to "implement a use case in C#", "implement UC-001 in .NET", "build a Blazor page", "create a Razor component for this use case", "create a Vertical Slice", or mentions Blazor, Razor, .NET 10, or a feature slice for a use case specification.