visual-audit

Audit UI quality gaps across ten ProtoPulse views using Chrome DevTools MCP.

1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/wtyler2505/ProtoPulse --skill visual-audit-wtyler2505
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: visual-audit
Source: https://github.com/wtyler2505/ProtoPulse/tree/main/.claude/skills/visual-audit
Command: npx skills add https://github.com/wtyler2505/ProtoPulse --skill visual-audit-wtyler2505

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run a comprehensive visual UI audit of all ProtoPulse views to uncover accessibility and UX issues, capturing state snapshots and consolidating findings.

Core Features & Use Cases

  • Executes a 107-step visual UI audit across all ProtoPulse views (Architecture, Schematic, Breadboard, PCB Layout, Component Editor, Procurement, Validation, Output, Sidebar, and Chat Panel).
  • Generates a prioritized visual-audit findings checklist to guide fixes and improvements.
  • Integrates with Chrome DevTools MCP to perform on-demand snapshots, contrast checks, focus-ring validation, and responsive testing.

Quick Start

Run the audit workflow against a running ProtoPulse dev server and produce a shareable visual-audit report.

Frequently Asked Questions about visual-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit UI accessibility issues across multiple application views?

A comprehensive visual UI audit systematically checks accessibility and UX issues across application views by capturing state snapshots, evaluating contrast and focus rings, testing responsive layouts, and consolidating prioritized findings into a shareable checklist report.

What does a visual accessibility audit check for in a web application?

A visual accessibility audit evaluates contrast ratios, validates focus-ring visibility, checks layout consistency, and tests responsive behavior across UI views. It captures state snapshots and produces a prioritized findings checklist to systematically guide accessibility and UX fixes.

Can I use Chrome DevTools to automate accessibility checks across different views?

Yes, Chrome DevTools MCP integration enables on-demand snapshots, contrast checks, focus-ring validation, and responsive testing across UI views. The audit procedure handles environment checks, load failures, and accessibility constraints to produce a structured visual-audit report.

How do I generate a prioritized accessibility findings checklist from a UI audit?

Generate a prioritized findings checklist by executing a structured visual audit across all UI views, capturing snapshots, evaluating contrast and focus rings, testing responsiveness, and consolidating results into a summary report with ranked accessibility and UX issues to guide fixes.

What happens if a view fails to load during a visual UI audit?

The visual audit procedure explicitly handles load failures and accessibility constraints by performing environment checks against the running dev server. Failures are logged in the summary report while the audit continues across remaining views to ensure complete findings coverage.

Do I need a running dev server to perform a visual accessibility audit?

Yes, a running dev server is required. The visual audit workflow runs against a live ProtoPulse dev server to capture snapshots, evaluate contrast and focus, test responsiveness, handle load failures, and generate the visual-audit-checklist and summary report.