domains / families / design / ux-audit
Walk through a live web app AS a real user to find usability + behavioural bugs that static reviews miss. REQUIRES proof of interaction (typing, clicking, sending, observing) before any verdict — a sweep that didn't interact terminates with verdict 'Incomplete'. Walks threads, exercises every element, runs the multi-pane stress matrix, visual polish sweep, component perfection checklist, automated a11y (axe-core), pragmatic performance budget (LCP/CLS/INP), scenario battery (11 scenarios), and stress recipes including the real-flavour data battery. Hard gates: console errors/warnings = 0, network 5xx = 0, layout collapse = 0, axe Critical/Serious = 0, perf budget green. Audit-the-audit meta-check rejects rushed reports. Each finding has reproduction steps, evidence path, and suspected code location. Trigger with 'ux audit', 'walkthrough', 'qa sweep', 'audit the app', 'dogfood this', 'check all pages', 'find what's broken', 'stress the UI'. Audit screens for UX issues using Nielsen's heuristics and modern mobile UX best practices
The two copies define different procedures for the same skill name. The first is an interaction-first live walkthrough that requires an Interaction Manifest, hard gates (console/network/a11y/perf), and a verdict state machine. The second is a static screen audit based on Nielsen's heuristics and mobile UX checklists, with a letter-grade output. Neither is a reproduction of the other, and crowning one would hide a real alternative.