product-design-audit

Name the product, the flow, and a destination (Figma or a local folder). The skill walks each step in a browser, captures and validates a screenshot per step, and writes notes covering strengths, UX issues, and accessibility risks tied to each image.

Yes. When Figma is the destination, screenshots are placed left to right in rows with step numbers and notes underneath, then wrapped in a titled section. A local copy of every screenshot is kept even when Figma succeeds.

No. The audit reports accessibility risks visible in screenshots, such as contrast or labeling concerns, but explicitly states what still needs testing. Full WCAG compliance cannot be claimed from screenshots alone.

The skill tries the in-app Browser first, then Chrome, and asks before falling back to Playwright. If no tool can capture a valid screenshot, it stops and reports the blocker instead of fabricating evidence.

Findings are limited to what screenshots and observed behavior show in the current run. Cached screenshots, prior chats, and memory are not accepted as evidence, and dynamic states that cannot be captured are reported as named blockers.