ux-ui-map-page-by-page

What problem does it solve? Mapping a web application's UI route-by-route often overloads the agent's context when screenshots and analysis accumulate, leading to lost or incomplete documentation. This Skill enforces a memory-safe workflow that processes exactly one route at a time, writing page docs and analysis requests immediately after each capture. ## Core Features & Use Cases - Page-by-page capture: Navigates one route at a time, capturing desktop, tablet, and mobile screenshots before moving on. - Structured artifact generation: Produces per-page Markdown docs, JSON analysis requests, and an append-only capture index under ux_ui_map/. - Scaffold and validate script: A Node.js helper scaffolds expected files for a page and validates that all three screenshots and docs exist. - Use Case: Ask the agent to generate ux_ui_map/ artifacts for all routes of the Next.js dev server; it captures each route, writes docs immediately, and never retains prior pages in context. ## Quick Start Ask the agent to capture the UI page-by-page and generate ux_ui_map artifacts for all routes of the running dev server.