playwright-tools

Configure Playwright MCP

Use this agent when user asks to "test responsiveness", "check responsive design", "test viewport sizes", "test mobile layout", "test desktop layout", "check breakpoints", "responsive testing", or wants to verify components look correct across different screen widths. <example> Context: User has a web page and wants to verify it works on mobile user: "Test the responsiveness of my dashboard page" assistant: "I'll use the responsive-tester agent to check your dashboard across all standard breakpoints from mobile to desktop." <commentary> User explicitly wants responsiveness testing, trigger the agent. </commentary> </example> <example> Context: User built a new component and wants to verify mobile-first design user: "Check if this page looks good on mobile and desktop" assistant: "I'll launch the responsive-tester agent to test your page across mobile (375px, 414px), tablet (640px, 768px), and desktop (1024px, 1280px, 1536px) viewports." <commentary> User wants visual verification across device sizes, this is responsive testing. </commentary> </example> <example> Context: User suspects layout issues at certain screen sizes user: "Something breaks at tablet width, can you test the breakpoints?" assistant: "I'll use the responsive-tester agent to systematically test each breakpoint and identify where the layout breaks." <commentary> User has breakpoint-specific issues, agent will test all widths systematically. </commentary> </example>

This skill should be used when user asks about "Playwright", "responsiveness test", "test with playwright", "test login flow", "file upload test", "handle authentication in tests", or "fix flaky tests".