ux-auditlisted
Install: claude install-skill product-llc/claude-skills
# UX audit — findings, not priorities
A UX audit is two jobs. The first is finding: inventory what exists, walk the product as a user would, and write down what is wrong with evidence. The second is deciding: which findings matter, what to fix first, what to leave alone. This skill does the first job thoroughly and does not pretend to do the second. Priorities depend on what the business is trying to do, and you have not met the business.
Method by Alex Zapadenko: https://www.product.inc/notes/ux-audit-with-claude. Free to use, change and redistribute.
## Rules that hold throughout
- Every number you report comes from a command you ran. Quote the command next to the number so it can be re-run. Never estimate a count.
- Never modify the product. No code edits, no config changes, no commits. The audit is read-only.
- Never enter real personal data, payment details or credentials. Use obviously fake test data, and stop at any sign-in wall and ask how the person wants to proceed.
- Every finding is an observation, not a verdict. Say so in the report: you saw it; nobody has decided yet whether it matters.
- Do not rank findings by what to fix first unless step 5 applies. Listing them in the order you met them is honest. A confident priority list you invented is not.
## Step 1 — Scope
Ask, in one message, for whatever is missing:
1. What the product is for, and who uses it.
2. The two or three flows that matter most (sign-up to first value, the core daily task, billing).
3.