visual-development-loop

Start the local app, capture a baseline screenshot and accessibility snapshot, make one change at a time, then capture the after-state with the same viewport and route. Check console errors, failed network requests, and layout regressions before concluding.

It prefers Playwright MCP for navigation, snapshots, and screenshots, uses browser-use MCP only when credentials exist, and falls back to CDP harnesses for Chromium or Electron debug-port work. Repo-native smoke tests provide the narrowest automated check.

Use CDP harnesses when working with Chromium or Electron debug ports or when you need low-level runtime signals that Playwright MCP cannot expose. Playwright MCP remains the default for standard navigation and interaction tasks.

Prefer inline summaries when screenshots, traces, or network bodies may contain private content. Save artifacts under /tmp/verify-this/<claim-slug>/ only when safe, name them by phase and viewport, and remove temporary browser profiles afterward.

Prefer stable selectors such as roles, labels, landmarks, and project-owned data-* attributes. Avoid coordinate clicks unless a fresh screenshot proves the target and no semantic selector exists.