Skip to content

jezweb/claude-skills / plugins/dev-tools/skills/ux-audit

ux-audit

Verified

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'.

references/stress-test-recipes.md

View on GitHub
# Extended Stress Test Recipes

Beyond the 9 scenarios in [scenario-tests.md](scenario-tests.md), these recipes catch the failure modes that scenarios miss. Each recipe has a how-to, what-it-catches, and severity guide.

Run all relevant recipes during Phase 5 of the audit. Skip recipes that genuinely don't apply (no print stylesheet on a chat app).

## 1. Race conditions

### Double-click submit

**How**: Click any Send / Save / Submit button twice in rapid succession (< 200ms apart).

**What it catches**:
- Duplicate creation (two records, two messages, two payments)
- Optimistic UI desync (one click goes through optimistically, second click finds the optimistic state and acts on it)
- Disabled-state race (button disables but second click already queued)

**Severity if it produces duplicates**: **Critical**.

### Fast-type then immediate blur

**How**: Type into an input, then `Tab` or click outside without waiting for autocomplete / validation.

**What it catches**:
- Validation that runs after blur but the form already submitted via Enter
- Autocomplete that completes after blur, leaving stale value
- onChange handlers firing after onSubmit

### Rapid navigation

**How**: Click a list item, then before it loads, click a different list item.

**What it catches**:
- Stale data shown (old item's data leaks into new item's view)
- Cancelled-fetch handling (TanStack Query / SWR — abort missed)
- Loading spinner stuck

## 2. Slow network (3G throttle)

**How**: Browser DevTools → Network → Slow 3G (or set request throttling to 100kbps download / 400ms latency).

**What it catches**:
- Loading states that disappear after 200ms (real users see them)
- Skeleton screens never showing (data arrives too fast in dev)
- Timeouts (button-disable for 60s with no progress hint)
- Retry UX (does it auto-retry? Should it?)
- Optimistic UI (does it work when the server takes 5s to confirm?)

**Severity guide**: missing skeleton on a list view that takes > 1s = High. Stuck spinner with no escape > 5s = Critical.

## 3. Reduced motion

**How**: Browser DevTools → Rendering → Emulate CSS media `(prefers-reduced-motion: reduce)` → matches.

**What it catches**:
- Animations that ignore the preference (still slide, still fade)
- Spring physics on scroll (causes motion sickness for users who set the pref)
- Auto-playing videos

**Severity if any animation runs when reduced**: High (accessibility violation).

## 4. i18n stress

### Long German nouns

**How**: Inspect the longest copy on each page and replace with a synthetic 50+ character string. Or, if i18n exists, switch to `de`.

**What it catches**:
- Truncation without tooltip (`overflow: hidden` cuts off important info)
- Wrap into 4+ lines breaking layout
- Buttons that grow beyond their parent container

### RTL Arabic

**How**: Set `dir="rtl"` on `<html>` (or switch to `ar` / `he` if i18n exists).

**What it catches**:
- Icons that should mirror but don't (chevron-right pointing wrong way)
- Layouts assuming left-to-right (sidebar on wrong side)
- Padding-left vs margin-inline-start drift

### CJK character widths

**How**: Replace copy with CJK strings (Chinese / Japanese / Korean) for the longest fields.

**What it catches**:
- Line-height insufficient for character ascenders
- Font-family fallback ugly in CJK
- Text rendering as squares (missing font subset)

## 5. Empty / saturated states

### Empty
- Lists with 0 items
- Conversations with 0 messages
- Projects with 0 files / tasks
- Search with 0 results
- New user with 0 history

### Saturated
- Lists with 1000+ items (pagination, virtualisation, performance)
- Conversation with 200+ messages (scroll-to-bottom, performance)
- Project with 50+ tagged categories (filter UX)

### Long content edges
- Single field with 100+ characters (overflow, tooltip, truncate)
- Single field with 5000-word paste (textarea behaviour, save semantics)
- Filename with special characters (`O'Brien.pdf`, `café.csv`, emoji, `<script>` injection check)

## 6. Offline mode

**How**: Browser DevTools → Network → Offline. Then perform an action.

**What it catches**:
- Silent failures (no error shown)
- Optimistic UI without rollback
- Queue / retry UX (Tauri / Notion / Linear show "queued" — does this app?)
- Lost work on subsequent reload

**Severity if data is lost silently**: Critical.

## 7. Print stylesheet

**How**: Browser DevTools → Rendering → Emulate CSS media → `print`. OR `Ctrl+P` to open the print preview.

**What it catches**:
- Invisible content (white text on white background after print rules apply)
- Sidebar / nav still showing (should typically be hidden)
- Page breaks landing mid-content
- Print-specific layout never tested

**Severity if no print rules and printing is plausible**: Medium (e.g. invoices, reports).

## 8. High-contrast / forced-colors mode

**How**: Browser DevTools → Rendering → Emulate CSS media → `forced-colors: active`. OR Windows High Contrast.

**What it catches**:
- Elements that disappear (background-only highlights without borders)
- Icons rendering as squares
- Focus rings invisible in forced colours
- Form inputs unstyleable

**Severity**: High accessibility violation.

## 9. Keyboard-only

**How**: Unplug the mouse. Walk the entire app with Tab / Shift+Tab / Enter / Space / Arrow keys / Escape.

**What it catches**:
- Focus traps in modals (can't Tab out)
- Hidden focus states (can't see where you are)
- Skipped focusable elements
- Custom dropdowns that don't respond to arrow keys
- Drag-and-drop with no keyboard alternative
- Modals that don't return focus to trigger on close

**Coverage check**: every interactive element must be reachable via Tab and operable via Enter / Space / Arrow.

## 10. Screen reader test (NVDA / VoiceOver)

**How**: Mac: VoiceOver (Cmd+F5). Windows: NVDA (free download).

**What it catches**:
- Unlabeled buttons ("Click here" landmarks, icons without aria-label)
- Decorative images announced
- Form fields with no associated label
- Dynamic content that doesn't announce changes (`aria-live`)
- Headings out of order (h1 → h3 skipping h2)

**Severity**: Major accessibility violation. Often Critical for compliance-required apps.

## 11. Long-press / right-click variations

**How**: Right-click on every interactive element. Long-press (touch device emulation).

**What it catches**:
- Context menus not implemented where they should be
- Default browser context menu showing on a custom widget
- Long-press selecting text on a card meant to be tappable
- Drag handles activating a context menu

## 12. Browser-back during in-flight action

**How**: Click Submit, then immediately click browser back before the action completes.

**What it catches**:
- Server still processes the action; user lands on previous screen with no idea
- Optimistic UI rolled back but server confirmed (state inconsistency)
- Navigation guards not present on dirty forms

**Severity**: High if data is created server-side without user confirmation.

## 13. Tab-restore (browser crash sim)

**How**: Close the browser tab mid-task. Reopen. Use browser's "Reopen Closed Tab" or navigate to the URL.

**What it catches**:
- Drafts not saved (autosave gap)
- "Continue where you left off" missing
- Local storage cleared on tab close
- Session lost (re-login required for an authenticated state)

## 14. Multiple-tab consistency

**How**: Open the app in two tabs side by side. Modify a record in tab A. Switch to tab B. Modify the same record.

**What it catches**:
- Stale state in tab B (no sync)
- Conflict resolution UX (last-write-wins silently)
- Real-time updates (or absence)
- Auth state divergence (logout in A, B doesn't notice)

## 15. Stale localStorage / IndexedDB

**How**: Modify a known localStorage / IndexedDB key to an old version's format. Reload.

**What it catches**:
- App crashes on schema mismatch
- Silent reset of user state
- Missing migration logic

**Especially relevant for**: apps that have been deployed for > 6 months with persistent client-state.

## 16. Real-flavour data battery

AI-built UIs are notoriously dev-data clean. Every form accepts "Test User" and "test@example.com" but breaks on real names, real lengths, real edge cases. Use the fixture below across every form and every list during element exhaustion.

### Fixture — paste each into appropriate fields

```
NAMES (test in name fields, mention pickers, member lists):
  O'Brien                          // apostrophe
  María                            // diacritic
  François                         // diacritic + cedilla
  朴기철                           // CJK + Hangul
  محمد بن سلمان                  // RTL Arabic
  Schöngeist-Holzhäusermeisterin   // 30+ char German compound
  X Æ A-12                         // unusual punctuation
  ' OR 1=1; --                     // SQL injection canary (must escape)
  <script>alert(1)</script>        // XSS canary (must escape)
  (200 chars of "a")               // length stress

EMAIL ADDRESSES (sign-up, invite, sharing):
  user+filter@example.com          // plus-addressing
  user.name@sub.domain.example.co.uk
  "user with space"@example.com    // quoted local-part (RFC 5321 valid)
  user@127.0.0.1                   // IP literal
  user@xn--80akhbyknj4f.xn--p1ai   // punycode

PHONE NUMBERS (contact forms):
  +61 4 1234 5678                  // AU mobile
  (02) 1234 5678                   // AU landline w/ area code
  04-1234-5678                     // AU mobile w/ dashes
  +1-555-555-5555 ext 1234         // US with extension
  +44 20 7946 0958                 // UK landline

ADDRESSES (shipping, billing):
  1/12 O'Connell St, Newcastle NSW 2300         // unit prefix + apostrophe
  Apt 4B "Rear Cottage", 123 Main St            // double-quote in line
  PO Box 1234                                   // PO box variant
  Lot 7 RMB 142, Williamtown NSW 2318           // rural mail bag

PASTE BOMBS (textareas, message fields):
  - 5,000-character paragraph (stress textarea height + serialisation)
  - 200-line paste with mixed indentation
  - Tab characters (preserves vs collapses?)
  - RTF clipboard paste from Word (does the editor keep formatting it didn't ask for?)
  - Smart quotes "" ‹›『』 (does the form normalise?)

FILES (uploads):
  - 8000×8000 PNG (memory blow-out test)
  - 50 MB PDF (size limit test)
  - "résumé (final)(2).pdf" (filename with spaces, parens, accent)
  - .heic photo (iOS native — does the app convert or reject cleanly?)
  - 0-byte file (edge: does upload code crash on empty buffer?)
  - .exe / .dmg (security: must reject)

NUMBERS (currency, quantities):
  $1,234.56                        // formatted
  1,234.56                         // ambiguous (1234.56 or 1.23456?)
  €1.234,56                        // EU format
  ¥1234                            // no decimals
  1.5e6                            // scientific notation
  -0                               // signed zero
  Infinity                         // edge

DATES (date pickers, timestamps):
  29 Feb 2024                      // valid leap year
  29 Feb 2025                      // INVALID — must reject
  31 Apr 2025                      // INVALID — only 30 days in April
  1 Jan 1900                       // far past
  31 Dec 2099                      // far future
```

### Where to use it

For every form discovered in element exhaustion:

1. Find the field type (name, email, address, etc).
2. Paste the most relevant fixture string.
3. Submit + verify:
   - Render after submit displays the input intact (no character loss / corruption)
   - Stored value round-trips on edit (open the saved record, re-edit, verify the field still contains the input exactly)
   - Validation errors are CLEAR (not "Invalid input" — say what's wrong: "Apostrophes not allowed" if that's the rule)
   - SQL/XSS canaries are escaped, not executed

### What it catches

- Validation that strips characters silently (apostrophe → `?`, accents → blank)
- Length truncation without warning (200-char name → first 50)
- Server-side encoding mismatches (utf8 → utf8mb4 issues)
- Search/sort that doesn't normalise diacritics ("Maria" doesn't find "María")
- File-type filters that reject legitimate formats (.heic, .webp)
- Clipboard paste that injects HTML / inline styles when not wanted
- Number/date parsers that silently coerce wrong values

### Severity guide

| Failure mode | Severity |
|---|---|
| User input silently lost / corrupted on save | Critical |
| User input rejected without clear error message | High |
| Display renders mangled (HTML entities visible, encoding garbage) | High |
| Search misses normalised matches (Maria/María) | Medium |
| File upload rejects legitimate format | Medium |
| Filename special chars displayed weirdly but file otherwise works | Low |

This recipe is **mandatory for any app accepting user content**. Skip only for builder-mode reference pages and read-only displays.

## Severity reference

A stress test produces findings whose severity follows these defaults:

| Recipe failure | Default severity |
|---|---|
| Double-click produces duplicates | Critical |
| Slow-network shows no skeleton | High |
| Reduced-motion ignored | High |
| Long German breaks layout | High |
| RTL mirroring missing on icons | Medium |
| Offline silently loses data | Critical |
| Print stylesheet absent (where plausible) | Medium |
| Forced-colors elements disappear | High |
| Focus trap in modal | Critical |
| Screen reader: unlabeled primary action | Critical |
| Tab-restore loses draft | High |
| Multi-tab: stale state | Medium |

Promote findings with stacked failures (e.g. slow-network AND no skeleton AND no progress text → Critical).

## When to skip a recipe

Skip recipes that don't apply:
- Print stylesheet on a chat app — skip
- RTL on an English-only app — skip but note that future i18n will need it
- Offline mode on a tool that legitimately requires connectivity — note the connection requirement instead

Don't skip recipes that *should* apply but the team hasn't implemented yet — those produce findings.

## Coverage publication

At the end of the stress phase, publish:

```
STRESS COVERAGE
  Recipes run: 13 / 15
  Skipped: 2 (RTL — no i18n yet; Print — chat-only app)
  Findings produced: 7 (1 Critical, 3 High, 2 Medium, 1 Low)
```

Coverage transparency lets the next agent know what wasn't tested.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall