marketplace

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", "test the JPA repository", or mentions MockMvc, MockMvcTester, RestAssured, RestTestClient, Testcontainers, @SpringBootTest, or server-side Java testing for this stack.

Creates end-to-end test case documents (TC-*.md) that chain several use cases into one user journey with a step-by-step Flow table, concrete test data, and final validations. Use when the user asks to "create a test case", "write a test case", "define an end-to-end scenario", "document a user journey for testing", "chain use cases into a test", or mentions a test case document, TC-001, journey test, or end-to-end test scenario. Also trigger whenever the user lists several use case IDs (UC-*) and wants one test definition spanning them — the resulting TC-* document is what e2e test skills (e.g. /playwright-test TC-001) automate.

Creates or updates PlantUML use case diagrams defining actors, use cases, and their relationships from requirements. Use when the user asks to "create a use case diagram", "draw a UML diagram", "map actors to use cases", "generate a .puml file", or mentions PlantUML, use case overview, actor diagram, or system use cases.

Creates detailed use case specification documents with actors, preconditions, main success scenarios, alternative flows, postconditions, and business rules. Use when the user asks to "write a use case", "specify a use case", "document system behavior", "define scenarios", "write a functional spec", or mentions use case specification, acceptance criteria, or user scenarios. Also trigger whenever the task is to write use case specification documents for the use cases in a use case diagram (e.g. docs/use_cases.puml) — including phrasings like "detailed use case specifications before writing any code", "one file per use case", or a request to cover the happy path, alternative flows, postconditions, and business rules for each use case.

Creates Vitest component tests for Angular views using Angular's own testing idioms — TestBed, ComponentFixture, and HttpTestingController — not React Testing Library patterns. Use when the user asks to "write frontend tests", "test the Angular component", "write a Vitest test", "unit test an Angular page", or mentions TestBed, HttpTestingController, or component testing for this stack.