frontend-playwright

Visual QA gate for frontend code. ALWAYS use before delivering any UI changes - navigate, screenshot, verify console is error-free. Use for: responsive testing across viewports, form/interaction testing, debugging hydration and render issues. Catches visual bugs before users see them.

⭐4stars🔀0forks📁View on GitHub🕐Updated Dec 22, 2025⬇️1downloads

When & Why to Use This Skill

The Frontend Playwright skill acts as a comprehensive Visual QA gate for web development, leveraging Playwright browser automation to ensure UI integrity. It enables developers to perform automated visual checks, monitor console errors, and validate responsive designs across multiple viewports. By integrating this skill into the development workflow, teams can identify hydration mismatches, rendering bugs, and broken interactions before code delivery, significantly improving frontend quality and user experience.

Use Cases

  • Visual Regression Testing: Automatically capture and review screenshots after UI changes to ensure components render correctly across mobile, tablet, and desktop viewports.
  • Pre-delivery Quality Assurance: Execute a mandatory checklist including console error verification and network request monitoring to guarantee a clean, error-free deployment.
  • Interactive Form Validation: Simulate complex user journeys by automating form inputs, button clicks, and state transitions to verify functional correctness.
  • Hydration and Rendering Debugging: Identify and resolve 'Hydration mismatch' or JavaScript execution errors by inspecting the live browser state and console logs during development.
namefrontend-playwright
descriptionVisual QA gate for frontend code. ALWAYS use before delivering any UI changes - navigate, screenshot, verify console is error-free. Use for: responsive testing across viewports, form/interaction testing, debugging hydration and render issues. Catches visual bugs before users see them.
allowed-toolsBash (*), mcp__playwright__browser_navigate, mcp__playwright__browser_snapshot, mcp__playwright__browser_take_screenshot, mcp__playwright__browser_click, mcp__playwright__browser_type, mcp__playwright__browser_console_messages, mcp__playwright__browser_network_requests, mcp__playwright__browser_resize, mcp__playwright__browser_evaluate, mcp__playwright__browser_wait_for, mcp__playwright__browser_hover, mcp__playwright__browser_close

Playwright MCP

Browser automation for visual verification. Self-check UI before delivering.

When to Use

  • After creating/modifying components → verify render
  • Before delivering code → final QA check
  • Debugging UI issues → see actual browser state
  • Responsive testing → check mobile/tablet/desktop

Process

NAVIGATE → VERIFY → FIX → DELIVER

1. Start dev server: npm run dev
2. browser_navigate → open page
3. browser_take_screenshot → visual check
4. browser_console_messages { onlyErrors: true } → MUST BE EMPTY
5. Fix issues if any → repeat
6. Deliver when clean

Tools Quick Reference

Navigation:
  browser_navigate:      { url: "http://localhost:3000" }
  browser_resize:        { width: 375, height: 812 }
  browser_wait_for:      { time: 2 } | { text: "Success" }
  browser_close:         {}

Inspection:
  browser_snapshot:           # Get element refs for interactions
  browser_take_screenshot:    { filename: "check.png", fullPage: true }
  browser_console_messages:   { onlyErrors: true }  # CRITICAL
  browser_network_requests:   {}
  browser_evaluate:           { function: "() => ..." }

Interaction:
  browser_click:   { element: "Submit button", ref: "e5" }
  browser_type:    { element: "Email input", ref: "e3", text: "user@example.com" }
  browser_hover:   { element: "Menu item", ref: "e8" }

Pre-Delivery Checklist

MUST PASS before delivery:
  ✓ browser_take_screenshot → looks correct
  ✓ browser_console_messages { onlyErrors: true } → EMPTY
  ✓ browser_network_requests → no 4xx/5xx
  ✓ Mobile viewport (375px) works

Common Workflows

Quick Verification

browser_navigate → browser_take_screenshot → browser_console_messages { onlyErrors: true }

Responsive Test

browser_resize { width: 375, height: 812 }  → screenshot
browser_resize { width: 768, height: 1024 } → screenshot
browser_resize { width: 1440, height: 900 } → screenshot

Form Test

browser_snapshot              # get refs
browser_type { ref, text }    # fill fields
browser_click { ref }         # submit
browser_wait_for { text }     # wait for result
browser_console_messages      # check errors

Common Console Errors

"Hydration mismatch":
  → Server/client render different
  → Fix: 'use client', useEffect for browser-only code

"Cannot read property of undefined":
  → Data not loaded
  → Fix: optional chaining, loading states

"Failed to fetch":
  → API error
  → Check: browser_network_requests for details

Viewport Sizes

Mobile:     { width: 375, height: 812 }   # iPhone
Tablet:     { width: 768, height: 1024 }  # iPad
Laptop:     { width: 1366, height: 768 }
Desktop:    { width: 1440, height: 900 }
Full HD:    { width: 1920, height: 1080 }

References

  • tools.md — Full MCP tools documentation with all parameters
  • workflows.md — Ready-to-use verification scenarios