Skill Wiki
ux-design
Domain inferred from 26 atoms across the corpora.
Atom counts by kind
| Kind | Count |
|---|---|
| principle | 10 |
| fact | 7 |
| taxonomy | 4 |
| anti-pattern | 2 |
| counter-example | 2 |
| source | 1 |
Sample atoms
Missing Empty State
Rendering an empty container — a blank table, an unstyled `<div>`, or just the page chrome with nothing inside — when a list, search, or workspace returns zero items.…
No Loading State
Triggering an async fetch, mutation, or navigation without any visible feedback — no spinner, skeleton, optimistic update, or disabled button.…
Counter Example Button No Loading
A typical submit handler that awaits a network request without any visible feedback. The button stays enabled, no spinner appears, the user can click it five times and trigger five duplicate POSTs.
Counter Example Empty List Blank
A React issue-list component that renders a `<ul>` with `items.map(...)`. When `items` is an empty array, the component renders an empty `<ul>` and the page goes silent. No headline, no CTA, no explanation.
Consistency Standards
Nielsen Heuristic 4 — Consistency and Standards: Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform and industry conventions.
Error Prevention
Nielsen Heuristic 5 — Error Prevention: Even better than good error messages is a careful design which prevents a problem from occurring in the first place.…
Flexibility Efficiency
Nielsen Heuristic 7 — Flexibility and Efficiency of Use: Accelerators — unseen by the novice user — may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experien…
Match Real World
Nielsen Heuristic 2 — Match Between System and the Real World: The system should speak the users' language, with words, phrases, and concepts familiar to the user, rather than system-oriented terms.…
Recognition Over Recall
Nielsen Heuristic 6 — Recognition Rather Than Recall: Minimize the user's memory load by making objects, actions, and options visible.…
User Control Freedom
Nielsen Heuristic 3 — User Control and Freedom: Users often choose system functions by mistake and will need a clearly marked 'emergency exit' to leave the unwanted state without having to go through an extended dialogue…
Visibility System Status
Nielsen Heuristic 1 — Visibility of System Status: The system should always keep users informed about what is going on, through appropriate feedback within a reasonable time.
Nielsen Aesthetic
Dialogues should not contain irrelevant or rarely needed information. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.