Frontend Testing
Use when the user asks about frontend testing, component tests with Testing Library, Vitest or Jest, userEvent, mocking APIs with MSW, Playwright or Cypress for critical journeys, and what to test in the UI. Produces a test strategy and component/E2E tests. Not for Storybook stories (use frontend-storybook) or cross-team E2E suites (use quality-e2e-testing).
Install
npx skills add j4flmao/agent-skills --skill frontend-testinggit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/frontend/universal/testing ~/.claude/skills/frontend-testingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Frontend Testing
## Purpose
Test user behavior, not implementation. Query elements the way users find them (by role, label, text). UserEvent simulates real interactions. Every component has an accessibility check.
## Agent Protocol
### Trigger
Exact user phrases: "frontend testing", "component test", "React testing", "Vue testing", "Angular testing", "testing library", "Cypress", "Playwright", "snapshot test", "what to test frontend".
### Input Context
Before activating, verify:
- The framework is known (React, Vue, Angular).
- The testing library is known (Testing Library, Playwright, Cypress) or can be inferred.
- The component or page being tested is specified.
### Output Artifact
No file output. Produces test code as text.
### Response Format
Test file:
```
describe('{Component}', () => {
it('should {expected behavior} when {condition}', () => {
// render
// interact
// assert
})
})
```
No preamble. No postamble. No explanations. No filler/hedging/transitions. Compress output — why use many token when few do trick.
### Completion Criteria
- [ ] Queries use getByRole, getByLabelText, or getByText (never getByTestId unless unavoidable).
- [ ] userEvent used instead of fireEvent.
- [ ] Each test has exactly one behavior assertion.
- [ ] Component tests cover: happy path, error state, empty state, loading state.
- [ ] E2E tests cover only critical user journeys (<10 per app).
- [ ] Accessibility assertion in every component test (axe-core).Details
- Skill name
frontend-testing- Repository
- j4flmao/agent-skills
- Path
skills/frontend/universal/testing/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Frontend Testing skill do?
Use when the user asks about frontend testing, component tests with Testing Library, Vitest or Jest, userEvent, mocking APIs with MSW, Playwright or Cypress for critical journeys, and what to test in the UI. Produces a test strategy and component/E2E tests. Not for Storybook stories (use frontend-storybook) or cross-team E2E suites (use quality-e2e-testing).
How do I install the Frontend Testing skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill frontend-testing. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Frontend Testing popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Rdma Roce
45j4flmao/agent-skills
Use when the user asks about RDMA, RoCEv2, InfiniBand, GPUDirect RDMA, ibverbs, PFC, ECN/DCQCN, lossless Ethernet or NCCL falling back to NET/Socket. Produces a fabric checklist, validation commands (perftest, nccl-tests) and NCCL env settings. Not for choosing DDP/FSDP parallelism (use distributed-training).
Fix Issue
45j4flmao/agent-skills
Fix a GitHub issue by number. Read the issue, implement the fix, write tests, commit.
Scala Play
45j4flmao/agent-skills
Use when the user asks about Play Framework, Scala Play controllers, Play JSON Reads/Writes, Slick, Guice DI in Play or Pekko streams in Play 3. Produces Play 3 services with async actions and tests. Not for Scala language basics (use lang-scala).
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.