When does the browser verification process trigger?

It triggers automatically during the /work loop after an implementation task modifies UI-related files like CSS, HTML, React, or Vue components.

What tools are required for Browser Verification to work?

This skill requires either Playwright MCP tools or Chrome Extension tools to be available for Claude to interact with a real browser environment.

Does it check for JavaScript errors?

Yes, part of the verification process includes checking the browser console for any JavaScript errors that occur during page load or interaction.

Can I bypass the verification if it flags a false positive?

Yes, it is an advisory tool rather than a hard gate. You can provide a reason for skipping the verification, which will be logged in the task notes.

What ports does the skill support for development servers?

By default, it looks for development servers running on ports 3000-8999, but this can be customized in the .pokayokay.json configuration file.

Automated Browser UI Verification

Name: Automated Browser UI Verification
Author: srstomp

bysrstomp

•

Security & Testing

Verifies UI changes automatically in a real browser to ensure frontend integrity and catch visual regressions during development.

About

The Browser Verification skill is an essential quality assurance component for the pokayokay orchestration plugin, designed to catch visual and functional issues before they reach the code review stage. By integrating directly into the Claude Code workflow, it automatically launches a real browser environment using Playwright or Chrome tools to validate UI-related changes in HTML, CSS, and modern framework files. This automated check prevents common issues like broken layouts, runtime JavaScript errors, and missing elements by providing a concrete pass/fail report based on actual browser rendering and interaction tests.

Key Features

Support for Playwright and Chrome Extension MCP tools
Real-time JavaScript console error monitoring
Configurable port ranges and path filtering for local dev servers
2 GitHub stars
Automated screenshot capture and visual analysis of UI changes
Intelligent trigger logic based on renderable file modifications

Use Cases

Validating CSS and layout consistency across components after styling refactors
Detecting runtime JavaScript crashes immediately after implementing interactive UI features
Ensuring local development server output matches the intended implementation spec

About

Key Features

Support for Playwright and Chrome Extension MCP tools
Real-time JavaScript console error monitoring
Configurable port ranges and path filtering for local dev servers
2 GitHub stars
Automated screenshot capture and visual analysis of UI changes
Intelligent trigger logic based on renderable file modifications

Use Cases

Validating CSS and layout consistency across components after styling refactors
Detecting runtime JavaScript crashes immediately after implementing interactive UI features
Ensuring local development server output matches the intended implementation spec