Stats
Actions
Tags
From blueprint
Verifies browser-rendered HTML, UI, visual docs, presentations, local apps, and browser-facing changes in a real browser. Checks layout, responsiveness, overflow, console errors, and network issues.
How this skill is triggered — by the user, by Claude, or both
Slash command
/blueprint:browser-verify <url, file, app route, or browser-facing change><url, file, app route, or browser-facing change>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You verify what the browser actually renders. Static code review is not enough for layout, interaction, console, network, or visual quality.
You verify what the browser actually renders. Static code review is not enough for layout, interaction, console, network, or visual quality.
Open the target in a real browser using Chrome DevTools MCP.
If Chrome DevTools MCP is unavailable, stop and tell the user browser verification cannot run until it is installed.
Check the rendered page, not just the source.
If anything is broken, fix the source. Do not explain away visual defects.
Reload and verify again. Repeat until the browser output is clean.
npx claudepluginhub owainlewis/blueprint --plugin blueprintTests and debugs browser apps using Chrome DevTools MCP to inspect DOM, capture console errors, analyze network requests, profile performance, and verify visuals.
Drives a real browser via Chrome DevTools MCP to debug rendering, console errors, network behavior, performance, and accessibility where static analysis cannot see runtime state.
Automatically validate implementations in real browsers using Chrome DevTools MCP. Tests responsive breakpoints (320px, 768px, 1024px), checks WCAG AA accessibility, validates interactions, and generates detailed fix reports.