charles-design-laws

Installation
SKILL.md

Goal

A screen or flow people get through without stopping to think: it shows only what their task needs, asks for nothing the app could work out, reads in groups at a glance, puts one thing first, and ends by telling them it worked. Each of the 20 laws below says what people do, what to build because of it, and how to check it, so building a screen and reviewing one walk the same steps.

The laws are as Jon Yablonski's Laws of UX states them, plus three from elsewhere: progressive disclosure (Jakob Nielsen), recognition over recall (Laws of UX's page on working memory, and Nielsen's sixth usability heuristic) and the default effect (Johnson and Goldstein, 2003). Motion, target sizes, how many choices to offer, chunking, conventions, messy input and response times are outside these 20 laws (charles-ux-animation covers them with Fitts's, Hick's, Miller's, Jakob's and Postel's laws and the Doherty threshold), so a problem there goes in the list of problems no law covers.

Steps

Walk steps 1 to 8 in order, every time. Each step works on what the one before it left: decide what's on the screen and what it asks of people before arranging it, arrange it before choosing what stands out, make each screen work before the flow across screens, and polish last. A later step never rescues an earlier one: a polished screen nobody can finish is still a screen nobody can finish. For a flow, run steps 2 to 5 on each screen, then step 6 across the whole flow.

Run every check on the rendered screen at the width most people use it at (a 390 × 844 px phone when you don't know), then re-run only the layout checks (Pareto, proximity, Von Restorff, the five-second look) at any other width it supports. The five-second look and "the place people look first" judge the first screenful. Judge layout and looks on the render, and behaviour (what a button does, what's saved, autofill hints) in the code. Each step says what it applies to; skip a law nothing in scope can trigger. In a build, a failed check means fix it and check again, and anything the request asked for gets built even when a law argues against it: build it, and name the law it breaks in what you deliver.

Reviewing instead? Change nothing, and walk the same steps. Every failed check and every broken Build rule is a finding. Later steps check what earlier findings would leave, so skip anything an earlier finding removes. Write each problem once, under the law whose rule names it (a tour goes under the paradox of the active user, not Occam's razor); when two laws name it, use the one in the earlier step. When a later finding removes something an earlier row fixed, drop the earlier row. Report the way Deliver says.

1. Name the job

Before changing or judging anything, write down:

Installs
34
GitHub Stars
229
First Seen
4 days ago