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.
Verifies UI changes in a real browser by checking visual elements, interactions, and console errors.
/plugin marketplace add srstomp/pokayokay/plugin install pokayokay@pokayokayThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/configuration.mdreferences/testability-detection.mdreferences/verification-flow.mdAutomatically 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.
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Search, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.