Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From pokayokay
Automatically verify UI changes in a real browser after implementation. Integrated into the /work workflow — checks visual elements, interactions, and console errors using Playwright. Not a standalone skill.
npx claudepluginhub srstomp/pokayokay --plugin pokayokayHow this skill is triggered — by the user, by Claude, or both
Slash command
/pokayokay:browser-verificationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Automatically verify UI changes in a real browser after implementation.
Drives a real browser to navigate, snapshot, interact, and capture evidence for end-to-end verification of web pages or web apps. Supports agent-browser, playwright-cli, or chrome-browser MCP.
Visually verify implemented features work correctly before marking complete. Use when testing UI changes, verifying web features, or checking user flows work in the browser.
Performs Playwright-driven visual checks, axe-core a11y audits, screenshot regression diffs, and E2E test scaffolds for UI-affecting changes.
Share bugs, ideas, or general feedback.
Automatically verify UI changes in a real browser after implementation.
This skill is triggered during the /work workflow after the implementer completes a task that modifies UI-related files. It is NOT a standalone skill - it's integrated into the work loop.
Catch visual and functional issues before code review by testing in a real browser. This prevents:
Browser verification only runs when ALL three conditions are met:
Must have either:
mcp__plugin_playwright_*)mcp__claude-in-chrome__*)Must have an HTTP server on a dev port (3000-8999) or ability to start one via package.json scripts.
Task must have modified files that affect browser output:
.html, .css, .scss, .less.tsx, .jsx, .vue, .svelte.hbs, .ejs, .pug)components/, views/, ui/, pages/If any condition fails, verification is silently skipped.
This is NOT a hard gate. If verification suggests issues but the user believes the implementation is correct:
Projects can customize in .pokayokay.json:
{
"browserVerification": {
"enabled": true,
"portRange": [3000, 9999],
"additionalPaths": ["src/templates/"],
"excludePaths": ["src/email-templates/"]
}
}
references/testability-detection.md - How to determine if verification should runreferences/verification-flow.md - Step-by-step verification processreferences/configuration.md - Project-level configuration optionsyokay-implementer → browser-verify → yokay-spec-reviewer → yokay-quality-reviewer → complete
Browser verification runs AFTER implementation and BEFORE spec review.