frontend-playwright

Automate visual QA verification for frontend UI changes across viewports.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/akhmat-s/Bantadthong-Vibes --skill frontend-playwright-akhmat-s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-playwright
Source: https://github.com/akhmat-s/Bantadthong-Vibes/tree/main/.claude/skills/frontend-playwright
Command: npx skills add https://github.com/akhmat-s/Bantadthong-Vibes --skill frontend-playwright-akhmat-s

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the risk of shipping visual bugs by automatically verifying UI components before delivery.

Core Features & Use Cases

  • Pre-Delivery Verification: Always run before delivering any frontend changes.
  • Use Case: Imagine you just built a new component. Use this Skill to automatically navigate to the page, take screenshots, and verify the console is error-free.

Quick Start

Navigate to 'http://localhost:3000' and verify the page renders correctly with no console errors.

Frequently Asked Questions about frontend-playwright

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate visual testing for frontend UI changes across different screen sizes?

Visual testing automates verification of UI components by capturing screenshots across responsive viewports, checking for layout breaks and rendering errors. This Skill navigates to your frontend, takes screenshots at multiple viewport sizes, and validates that components display correctly without visual bugs before deployment.

Can I catch console errors and rendering issues automatically during frontend testing?

Yes. Automated visual QA verification captures console errors, network activity, and render-accuracy issues alongside screenshots. This Skill checks for JavaScript errors, network failures, and hydration problems to ensure your UI is production-ready.

What's the best way to verify form interactions and component behavior work correctly?

Element interaction testing automates form submissions, button clicks, and state changes by navigating components and capturing their visual state at each step. This Skill simulates user interactions, takes screenshots to confirm UI responds correctly, and validates all behavior before users see it.

Do I need to manually test every viewport size to catch responsive design bugs?

No. Responsive testing automation eliminates manual viewport testing by programmatically rendering your UI across multiple screen sizes and comparing visual output. This Skill handles viewport control and screenshot capture automatically, catching layout shifts and responsive failures at scale.

How do I verify my frontend renders correctly on first load without hydration errors?

Render-accuracy validation checks that your page loads without errors and displays as intended by navigating to the URL, capturing screenshots, and verifying console state. This Skill confirms hydration completes successfully and visual output matches expectations immediately after page load.

What happens if visual bugs slip through to production—how do I prevent that?

Pre-delivery verification gates prevent visual bugs by running automated checks before any frontend change ships. This Skill acts as a QA checkpoint: navigate, screenshot, validate console and rendering—catching issues before users encounter them.