ux-lawslisted
Install: claude install-skill whoiscarlo/agent-skills
# UX Laws
The laws of UX as build rules. Each law has: **the rule**, why it holds, what to
build (with numbers where they exist), and a **check** to run in review.
Source: the laws are collected and named on Jon Yablonski's *Laws of UX*
(lawsofux.com) and in the original research each law cites. Wording here is my
own.
## How to use this skill
- **Building:** before writing a screen, read the group headings below and ask
which laws the screen touches. Most screens touch 5 to 8.
- **Reviewing:** run every **Check** line against the screen. Report failures
as "Law: what is wrong, where, the fix".
- These laws pull against each other sometimes (Hick wants fewer choices,
Jakob wants the familiar full menu). When they conflict, the user's main task
on that screen wins.
- Pair with `usability-principles` (Krug and Norman) for page-level review and
`refactoring-ui` for visual polish.
---
## Group 1: Choice and memory
### 1. Hick's law
**Rule: The more options you show at once, the longer the decision takes.**
Why: decision time grows with the number and complexity of choices.
Build:
- One primary action per screen. Everything else is visually quieter.
- Top navigation: 5 to 7 items. Move the rest into a "More" menu or footer.
- Long lists of options: add search, filters, or a "recommended" pick on top.
- Onboarding: one question per step, not one long form.
**Check:** Count the clickable choices above the fold. More than about 7 that
look equally important is a fail