ux-audit

Audits live web apps through real user interaction to find usability and behavioral bugs.

1|Updated Aug 18, 2026
One-click install
npx skills add https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent --skill ux-audit-scsm-unrestrict
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-audit
Source: https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent/tree/main/frontend-engineer/skills/ux-audit
Command: npx skills add https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent --skill ux-audit-scsm-unrestrict

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Static code reviews and DOM sweeps miss behavioral bugs that only surface when a real user types, clicks, and navigates. This Skill walks through a live web app as a locked persona, requiring proof of interaction before any verdict, so silent failures like dead buttons, stale caches, and layout collapses are actually caught. ## Core Features & Use Cases - Interaction-first walkthrough: A mandatory Interaction Manifest logs every typed input, clicked action, console read, and screenshot per page; without it the only legal verdict is Incomplete. - Hard quality gates: Auto-fail thresholds for console errors, network 5xx, layout collapse, axe-core Critical/Serious violations, and a pragmatic performance budget (LCP, CLS, INP). - Structured stress coverage: An 11-scenario battery (keyboard-only, heavy data, destructive confidence, round-trip workflows, data seasoning) plus multi-pane viewport stress and automated axe-core accessibility scans. - Use Case: Before shipping a new dashboard, run a full audit that walks every route as a first-time user, exercises all 31 interactive elements, and returns a ranked Top 5 findings list with reproduction steps, evidence paths, and suspected code locations. ## Quick Start Ask the agent to run a UX audit of your deployed app as a specific persona, for example: audit the app at its live URL as a busy first-time user and report every Critical and High finding.

Frequently Asked Questions about ux-audit

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

FAQPage Schema
How do I audit a web app for usability bugs with an AI agent?

Run an interaction-first walkthrough where the agent types into inputs, clicks primary actions, opens modals, and reads the console on every page. Each step is logged in an Interaction Manifest with timestamps and screenshots, and findings include reproduction steps and suspected code locations.

What browser tools does a UX audit need for authenticated apps?

Authenticated apps use Chrome MCP, which reuses your real logged-in Chrome session so OAuth and cookies work. Public sites can use Playwright MCP, and headless runs can inject test-auth cookies if the project exposes a gated test-auth endpoint.

Can axe-core replace manual accessibility testing?

No. axe-core catches roughly 80 percent of structural issues like contrast failures and missing aria-labels in under a second per page, but it cannot judge tab-order quality, focus trap behavior, or screen-reader announcement meaning. Pair it with a keyboard-only manual walkthrough.

Why does an audit return an Incomplete verdict?

A verdict is Incomplete when the Interaction Manifest is missing required entries, a phase was skipped, or the audit-the-audit meta-check fires, such as manifest timestamps clustered under 0.5 seconds apart. An Incomplete verdict cannot be upgraded to Pass regardless of how clean the app looked.

What performance thresholds fail a UX audit?

The pragmatic budget hard-gates LCP above 4.0 seconds, CLS above 0.25, and INP above 500 milliseconds, measured once on a representative route. These sit well above broken but below strict Core Web Vitals targets, suiting app interiors rather than marketing pages.