← ClaudeAtlas

claude-ux-measurelisted

Measures paint, processor, and layout cost against a running interface and reports numbers against published thresholds. Detects the project's existing browser harness rather than requiring one. Use when asked "how fast is this page", "measure the UI", "what does this cost to render", "check Core Web Vitals", or "profile the interface". Do NOT use to judge UI quality by reading source, which is `claude-ux-audit`.
erclx/canon · ★ 2 · Web & Frontend · score 68
Install: claude install-skill erclx/canon
# Claude UX measure Report numbers. A sentence about what the source looks like is what this exists to replace, so every finding is a reading beside the threshold it is measured against. ## Guards - If the project names no command that serves an interface and the user names no URL, stop: `❌ Nothing to serve. Name a running URL or a command that starts one.` Test for a servable interface rather than for source under a particular folder, since this measures what a browser receives and never reads the tree that produced it. - If the request is about intent, consistency, missing states, or contrast, run nothing and name `claude-ux-audit`. That skill reads source and this one runs the interface. ## Step 1: reach the interface Read these in parallel from the project root, skipping any that do not exist: - `package.json`: the `scripts` block naming a dev, preview, or start command - `.claude/context/development/`: the documented run commands and the port each serves - `CLAUDE.md`: project type and conventions Prefer a production-shaped build (`preview`, `start`) over the dev server. A dev server ships unminified modules and reports a cost no user pays. Ask for the URL when nothing names one. Do not guess a port. Then reach it. Request the URL first and measure whatever already answers, since a server the user started is the one they mean. Build and start the chosen command only when nothing answers, wait for it to accept a request before going on, and stop it once Step 4 ha