UX Design
UX pass for one feature of a macOS app, covering names, flow, where it opens (inline...
Install
npx skills add daveebbelaar/bama --skill ux-design -g -a claude-code -y- Repository
- daveebbelaar/bama1.3k
- Category
- Design
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 1,718 tokens
- Runs scripts
- No, instructions only
What it does
UX pass for one feature of a macOS app, covering names, flow, where it opens (inline, popover, sheet, window, alert), states, words, hover help, accessibility, and AI features. Use before coding a story that adds a screen, an action, or text, when user-stories or improve-loop call it, or when the user asks for a UX review, clearer wording, better names, or whether something should be a modal.
UX design
A feature that works can still confuse people. This pass decides what things are called, how a person moves through the feature, where it opens, and what it says, before any code exists.
Run it once per story that adds a screen, an action, or words. The output
is a UX: block in the story in docs/STORIES.md, plus new terms in
docs/GLOSSARY.md. To review a built screen, run the same steps against
its snapshot and list what fails, most serious first.
0. Read
Read docs/BRIEF.md, docs/GLOSSARY.md (create it if missing), the story,
and its reference screenshots.
1. Name it
Every thing in the app has exactly one name, and every name lives in the glossary.
| Term | Means | Not |
| --- | --- | --- |
| Task | One thing to do, with an optional due date | to-do, item, entry |
| Complete | Mark a task done; it leaves the list | check, finish, close |
- Name the things first (the nouns in the brief), then the actions on them.
- Use the user's words, not the code's: "Task", not "TaskEntity" or "record".
- Use Apple's words for system actions: Settings, Quit, Close, Undo, Move to Trash (when it can come back), Delete (when it cannot).
- One word per idea across buttons, menus, titles, tooltips, and errors.
- Name a feature for what it does for the person, not the technology. A toggle gets a verb phrase that says what and for whom ("Enhance Dialogue", not "Isolate Vocals"). Say the name in a sentence out loud. Method: writing.md.
Check: every noun and verb the story puts on screen is in the glossary, and no glossary term has a second name anywhere.
2. Map the flow
Write the flow as one line, from every way in to a clear end.
Command-N, toolbar +, File > New Task -> title field has focus -> Return saves, row appears -> focus stays for the next task
