ui-testlisted

Runs UI tests described in plain English by driving real Chrome via the Claude-in-Chrome extension. Covers end-to-end flows (clicks, forms, assertions), visual checks (screenshot + optional baseline diff), accessibility (axe-core), performance (Web Vitals + light Lighthouse-style metrics), and an interactive --debug mode that tails console + network and surfaces issues without needing explicit assertions. Accepts inline descriptions or test files in `./tests/ui/*.md`. Per-run folders contain artifacts (screenshots, console, network, axe report, perf metrics) plus a single-file 2026-aesthetic HTML report with a verdict-forward layout. Learns from per-run feedback — false-positive categories, screenshot strategy, severity floors, and per-project baselines personalize future runs. Use when the user wants to verify a UI flow, screenshot a regression, audit accessibility, profile a page, or debug something visibly broken in a real browser session.
mostafa-drz/claude-skills · ★ 4 · Web & Frontend · score 76

Install: claude install-skill mostafa-drz/claude-skills

## Preferences _On startup, use Read to load `~/.claude/skills/ui-test/preferences.md`. If missing, treat as first-run (see First-time detection)._ Defaults when no preferences exist: - `output-root`: `./test-results/ui-test/` (cwd-relative when in a project; falls back to `~/.claude/skills/ui-test/runs/` outside a project) - `viewport`: `1440x900` (single) — accepts a comma list for matrix runs (e.g. `375x812,1440x900`) - `categories`: `e2e,visual,a11y,perf` (debug is a separate mode, not a category) - `screenshot-strategy`: `per-step` (per-step / on-fail / never) - `a11y-severity-floor`: `serious` (minor / moderate / serious / critical — anything at-or-above is a failure) - `perf-budget`: `lcp<=2500,cls<=0.1,inp<=200,js-heap<=50mb` — overridable per-run via `--perf-budget` - `verbosity`: `verbose-on-failure` (concise / detailed / verbose-on-failure) - `spec-priority`: `inline-first` (inline-first / project-first / both) - `auto-baseline`: `true` (record on first run, diff thereafter) - `auto-open-report`: `true` - `confirm-plan`: `always` (always / only-multi-step / never) _Also load `~/.claude/skills/ui-test/feedback-journal.md` if present — surface the one-line `Signal:` from the latest 5 sessions to bias defaults (false-positive categories get pre-deselected, baselines flagged-as-flaky get re-recorded, etc.)._ ## Context _On startup, use Bash to detect: today's date (`date +%Y-%m-%d-%H%M`), the current working directory (`pwd`), whether `./tests/ui/` exists, whether