spring-testing-router
Use this skill proactively before writing any Spring test code — even without an explicit request. Triggers: about to create test files for a Spring Boot project, writing a JUnit test suite, implementing test coverage for a Spring application, or whenever the user mentions writing Spring tests. Do not wait for the user to name a specific slice annotation. Routes to: spring-jpa-testing (JPA repositories, org.springframework.boot.data.jpa.test.autoconfigure.DataJpaTest, org.springframework.data.jpa.repository.JpaRepository), spring-mvc-testing (org.springframework.boot.webmvc.test.autoconfigure.WebMvcTest, org.springframework.test.web.servlet.MockMvc, REST controllers), spring-security-testing (org.springframework.security.test.context.support.WithMockUser, CSRF, JWT, OAuth2), spring-webflux-testing (org.springframework.boot.webflux.test.autoconfigure.WebFluxTest, org.springframework.test.web.reactive.server.WebTestClient, reactor.test.StepVerifier), spring-websocket-testing (STOMP, SockJS, WebSocket messaging), spring-testing-fundamentals (org.assertj.core.api.Assertions, org.mockito.BDDMockito, testing pyramid, context caching).
Works with
--- name: spring-testing-router description: Use this skill proactively before writing any Spring test code — even without an explicit request. Triggers: about to create test files for a Spring Boot project, writing a JUnit test suite, implementing test coverage for a Spring application, or whenever the user mentions writing Spring tests. Do not wait for the user to name a specific slice annotation. Routes to: spring-jpa-testing (JPA repositories, org.springframework.boot.data.jpa.test.autoconfigure.DataJpaTest, org.springframework.data.jpa.repository.JpaRepository), spring-mvc-testing (org.springframework.boot.webmvc.test.autoconfigure.WebMvcTest, org.springframework.test.web.servlet.MockMvc, REST controllers), spring-security-testing (org.springframework.security.test.context.support.WithMockUser, CSRF, JWT, OAuth2), spring-webflux-testing (org.springframework.boot.webflux.test.autoconfigure.WebFluxTest, org.springframework.test.web.reactive.server.WebTestClient, reactor.test.StepVerifier), spring-websocket-testing (STOMP, SockJS, WebSocket messaging), spring-testing-fundamentals (org.assertj.core.api.Assertions, org.mockito.BDDMockito, testing pyramid, context caching). license: Apache-2.0 --- # Spring Testing Skill Router Route based on what the user is testing. If no specific slice annotation is visible and the domain is unclear, default to `spring-testing-fundamentals`. ## Routing Table | The user is testing... | Load this skill | |------------------------|-----------------| | JPA repositories, Spring Data queries, database persistence | `spring-jpa-testing` | | REST controllers, HTTP endpoints, MockMvc | `spring-mvc-testing` | | Authentication, authorization, CSRF, JWT, OAuth2 | `spring-security-testing` | | Reactive endpoints, WebClient, SSE, R2DBC | `spring-webflux-testing` | | WebSocket, STOMP messaging | `spring-websocket-testing` | | AssertJ idioms, Mockito patterns, test pyramid, general Spring testing | `spring-testing-fundamentals` | ## Slice Annotation Signals If any of these annotations appear in the code or question, route immediately to the corresponding skill: - `@DataJpaTest` → `spring-jpa-testing` - `@WebMvcTest` → `spring-mvc-testing` - `@WebFluxTest` → `spring-webflux-testing` - `@SpringBootTest(webEnvironment = RANDOM_PORT)` with STOMP → `spring-websocket-testing` - `@WithMockUser`, `@WithUserDetails` → `spring-security-testing` ## Default Fallback If the domain is ambiguous and no slice annotation is visible, load `spring-testing-fundamentals`. It covers testing pyramid guidance, context caching, anti-patterns, and AssertJ/Mockito idioms that apply across all Spring testing scenarios.
More Testing skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
setup-pre-commit
mattpocock/skills
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

