← ClaudeAtlas

auditing-site-navigationlisted

Use when auditing a website's navigation, information architecture, or usability, or when overhauling it and intending to claim a measurable before/after improvement. Also use when scoring a site per-persona, or dispatching UI fixes to parallel agents.
lucasyhzhu-debug/claude-skills · ★ 0 · AI & Automation · score 70
Install: claude install-skill lucasyhzhu-debug/claude-skills
# Auditing Site Navigation ## Overview Agents already audit sites well. Left alone they read routing config correctly, verify claims at file:line, reproduce failure states live, and refuse to invent facts about the owner. **This skill teaches none of that.** What they do not build unprompted is a *measurement instrument*. They invent personas mid-run, score by gestalt, label an unweighted mean "weighted", and persist nothing. The findings are reproducible; the numbers are not. Any later "we went from 55 to 78" is then unfalsifiable, and a regression introduced while fixing goes undetected. **Core principle: the observations are the easy half. A score is only worth stating if a different agent, next month, can recompute it.** ## Step 1: copy the workflows in. Do this before reading further. ```bash mkdir -p <target-repo>/.claude/workflows cp <this-skill-dir>/workflows/*.js <target-repo>/.claude/workflows/ ls <target-repo>/.claude/workflows/ # confirm three files ``` **Do this first, literally.** In testing, an agent read this skill, agreed with it, hand-followed the Finding Contract from memory — and never copied the workflows. Its output then failed on exactly the fields the schema enforces: a cluster table with three undetected file-ownership collisions, three defects deducting zero points, and a baseline whose shape did not match what the rescore consumes. It complied with everything it could remember and missed everything it could not. Copy the files. | Wo