ux-design

1# UX design
2 
3A feature that works can still confuse people. This pass decides what
4things are called, how a person moves through the feature, where it opens,
5and what it says, before any code exists.
6 
7Run it once per story that adds a screen, an action, or words. The output
8is a `UX:` block in the story in `docs/STORIES.md`, plus new terms in
9`docs/GLOSSARY.md`. To review a built screen, run the same steps against
10its snapshot and list what fails, most serious first.
11 
12## 0. Read
13 
14Read `docs/BRIEF.md`, `docs/GLOSSARY.md` (create it if missing), the story,
15and its reference screenshots.
16 
17## 1. Name it
18 
19Every thing in the app has exactly one name, and every name lives in the
20glossary.
21 
22```markdown
23| Term | Means | Not |
24| --- | --- | --- |
25| Task | One thing to do, with an optional due date | to-do, item, entry |
26| Complete | Mark a task done; it leaves the list | check, finish, close |
27```
28 
29- Name the things first (the nouns in the brief), then the actions on them.
30- Use the user's words, not the code's: "Task", not "TaskEntity" or "record".
31- Use Apple's words for system actions: Settings, Quit, Close, Undo, Move
32  to Trash (when it can come back), Delete (when it cannot).
33- One word per idea across buttons, menus, titles, tooltips, and errors.
34- Name a feature for what it does for the person, not the technology. A
35  toggle gets a verb phrase that says what and for whom ("Enhance
36  Dialogue", not "Isolate Vocals"). Say the name in a sentence out loud.
37…