Builds the client layer of a use case (UC-XXX) in a Spring Boot application: for every external system its Secondary Actors line names and docs/architecture/stack.md maps under External systems, an outbound port in the business module and an adapter that calls the system as its contract says — an OpenAPI operation through RestClient or an @HttpExchange interface, an AsyncAPI channel through a Kafka or AMQP producer. The adapter maps the provider's DTOs to domain records, so no provider type crosses the port, and turns the alternative flows the system causes (rejection, timeout, unavailable) into domain exceptions; it decides no retry policy alone. Use when the user asks to "call the payment provider", "integrate an external API", "write a REST client", "build the outbound adapter", or mentions RestClient, @HttpExchange, an external system as secondary actor, or a provider's OpenAPI or AsyncAPI file in a project that combines layer plugins. Normally run by /use-case-implement before the service layer.

Writes the client layer tests of a use case (UC-XXX) in a Spring Boot application: for each external system the use case calls, adapter tests against a stub of the provider's contract — MockRestServiceServer or WireMock for an OpenAPI operation, the broker's test setup for an AsyncAPI channel — that check the request on the wire, the mapping to domain records, and every alternative flow the system causes (rejection, timeout, unavailable); plus a reusable in-memory fake of the outbound port that the service, API, and UI tests put in place of the real adapter, so no test reaches the real system. Classes are named <System>ClientTest and every method carries @UseCase. Use when the user asks to "test the REST client", "test the payment provider adapter", "stub the external system", "write WireMock tests", or mentions MockRestServiceServer, WireMock, a fake of an outbound port, or contract-based client tests in a project that combines layer plugins. Run by /use-case-test before the integration layer.

Implements the REST API layer of a use case (UC-XXX) in a Spring Boot application: @RestController endpoints on top of the service layer, request and response DTO records, @Valid input validation, error mapping to RFC 9457 Problem Details with a @RestControllerAdvice, a status code per alternative flow, and paging. Takes the base path and contract style from the API contract section of docs/architecture/stack.md, and builds an operation the use case's **API:** line links in an agreed OpenAPI contract exactly as written; holds no business rule the service does not enforce. Use when the user asks to "build the REST API", "create an endpoint", "expose the use case over HTTP", "add a controller", "map errors to Problem Details", or mentions @RestController, @RequestMapping, DTOs, ProblemDetail, RFC 9457, status codes, or a JSON contract for a separate client such as Angular. Normally run by /use-case-implement after the service layer; it can also be run directly.

Builds the persistence layer of a use case (UC-XXX) with jOOQ: one @Repository per aggregate with an injected DSLContext, type-safe queries against the classes jOOQ generates from the Flyway migrations, projections into Java records with Records.mapping, MULTISET for nested collections, paging and dynamic filters, optimistic locking when the entity has a version, and UC-XXX BR-YYY markers on the query conditions that enforce a business rule. Transactions stay with the service layer. Hands the repository method signatures and record types to the service layer. Normally run by /use-case-implement after the migration layer; can be run directly. Use when the user asks to "write the jOOQ repository", "implement the data access for UC-001", "add a jOOQ query", "map the result into a record", "set up jOOQ code generation", or mentions jOOQ, DSLContext, Records.mapping, multiset, or a repository in a project that combines layer plugins.

Writes the persistence layer tests of a use case (UC-XXX) for jOOQ repositories: integration tests against a real database (Testcontainers PostgreSQL or the project's database) with @SpringBootTest or @JooqTest, test data from Flyway test migrations, expected values from the specification and the test data, classes named UC<id><Name>RepositoryTest and every method annotated @UseCase. Tests only queries with logic of their own — filters, joins, projections, MULTISET, paging, optimistic locking — not what the integration layer's tests already cover. /use-case-test runs it only to reconcile existing tests, for queries the integration layer cannot reach, or when the persistence layer is named; can be run directly. Use when the user asks to "test the jOOQ repository", "write repository tests for UC-001", "test this query against the database", or mentions jOOQ repository tests, @JooqTest, DSLContext tests, or Testcontainers tests of the data access in a project that combines layer plugins.

Scaffolds and configures a Vue 2.7 + Vuetify 2.7 frontend built with Vite 7 and Axios, with pinned versions, the vite.config.js alias and dedupe for Vue, the main.js bootstrap with new Vue and new Vuetify, MDI icons, VITE_ environment variables and an axios API module. Use when creating a frontend with Vite for a project that requires Vue 2 or Vuetify 2, migrating a Vue 2 app from Vue CLI to Vite, adding or upgrading dependencies in a Vue 2 project, setting up ESLint for Vue 2, or fixing errors such as Multiple instances of Vue detected, Vuetify is not properly initialized, or an npm peer conflict on vite.

Builds Vue 2.7 + Vuetify 2 screens with the correct v2 props, slots and events and with Vue 2 reactivity, for example a point-of-sale screen with product search, a table of editable sale lines, a total, a confirmation dialog, forms and snackbars. Covers v-data-table headers and item slots, v-autocomplete with server search, v-dialog activators, v-form validation, v-snackbar, custom v-model with value and input, and array updates with splice or $set. Use when writing or reviewing .vue components in a Vue 2 or Vuetify 2 project, when a Vuetify prop or slot seems to do nothing, when a table does not update after a change, or when porting a Vue 3 or Vuetify 3 example to Vue 2.