Audit UI and Save Files

Disciplined visual QA of a running web app, with a durable on-disk artifact and an explicit fix-dispatch step.

Dispatch parallel audit subagents that each drive the run-agent-browser skill across an owned slice of pages, capture screenshots at canonical viewports, and write one markdown finding per real bug into a dated, context-scoped, device-scoped tree under css-issues/. When the audit returns, cluster findings into themes, present a Markdown dispatch table, ask the user to approve, and only then spawn fix subagents that route to the pack's build-*, create-design-md, or direct-edit paths as appropriate.

The skill owns three things: where files live, how findings are written, and how the fix-pass is dispatched. It does NOT own design taste (the subagents bring that) and does NOT perform the fixes itself (it dispatches them).

When to Use

Trigger on phrases and contexts like:

• "audit the UI and save findings", "find CSS issues across the app and write them up"
• "do a visual QA and prepare fix tasks", "do a design QA pass and queue the fixes"
• "screenshot every page across viewports and inventory the bugs by date"
• "check responsive breakpoints on the whole site, then plan the fixes for me to approve"
• "the site is feature-complete — audit, save findings, and ask before fixing"
• "go through every page at desktop and mobile, write bug files, and propose fix subagents"