What problem does it solve?
This Skill removes the manual burden of collecting visual proof for product analysis, so teams can review pages, controls, dialogs, and state changes with consistent evidence instead of memory or screenshots taken ad hoc.
Core Features & Use Cases
- Page and route traversal: Walk a runnable app or supplied prototype and capture stable screenshots for each reachable view.
- Interaction evidence: Record what happens after clicks, tabs, menus, dialogs, uploads, exports, loading states, errors, and disabled guards.
- Parity and comparison work: Separate baseline and current evidence for PoC-to-product checks, UI iteration review, and before/after comparisons.
- Output packaging: Write organized screenshot folders, indexes, README notes, and contact sheets so downstream analysis can cite the evidence reliably.
Quick Start
Ask the capture skill to traverse the target app and collect page-by-page screenshots, interaction states, and contact sheets for the specific feature intake slug you want analyzed.