refactor(rules): split ui-ux.md into index + references
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
a2b9a9f5c4
commit
01220cebd4
8 files changed
+313
-306
No files matched your search
@@ -0,0 +1,64 @@
|
||||
# UI & UX Guidelines
|
||||
|
||||
* Design for clarity first.
|
||||
* Prefer simple, modern and predictable interfaces.
|
||||
* Optimize for fast understanding and low cognitive load.
|
||||
* Every screen should have a clear primary purpose.
|
||||
* Every important action should be easy to discover.
|
||||
* Prefer familiar interaction patterns over novel ones.
|
||||
* Do not require users to learn unnecessary custom behavior.
|
||||
* Keep layouts visually calm and structured.
|
||||
* Use consistent spacing, typography, colors and interaction patterns.
|
||||
* Avoid visual noise.
|
||||
* Avoid decorative elements that do not improve usability.
|
||||
* Avoid unnecessary complexity in navigation and workflows.
|
||||
* Minimize the number of steps required to complete common tasks.
|
||||
* Keep related information and actions close together.
|
||||
* Group content logically.
|
||||
* Use clear visual hierarchy.
|
||||
* Make primary actions visually distinct from secondary actions.
|
||||
* Avoid giving multiple actions equal visual priority when one is clearly more important.
|
||||
* Use whitespace intentionally.
|
||||
* Prefer readable line lengths and sufficient spacing.
|
||||
* Avoid dense walls of content.
|
||||
* Avoid oversized empty areas that reduce information efficiency.
|
||||
* Keep important information visible without unnecessary scrolling where practical.
|
||||
|
||||
## Design Decision Rule
|
||||
|
||||
* Every UI element should have a clear purpose.
|
||||
* Every additional interaction adds cognitive cost.
|
||||
* Prefer removing complexity over explaining unnecessary complexity.
|
||||
* Prefer familiar patterns over clever ones.
|
||||
* Prefer fewer clear choices over many ambiguous choices.
|
||||
* Prefer predictable behavior over surprising automation.
|
||||
* If a design decision introduces ambiguity, unnecessary complexity, or multiple equally valid UX directions, ask the user instead of deciding autonomously.
|
||||
|
||||
## Priority Order
|
||||
|
||||
Prioritize UI/UX decisions in this order:
|
||||
|
||||
* Correctness
|
||||
* Clarity
|
||||
* Safety
|
||||
* Accessibility
|
||||
* User control
|
||||
* Task efficiency
|
||||
* Consistency
|
||||
* Responsiveness
|
||||
* Visual polish
|
||||
|
||||
Visual polish must never reduce usability.
|
||||
|
||||
## Detailed guidance
|
||||
|
||||
Read the matching reference file before working in that area:
|
||||
|
||||
| Read this reference for... | ...this kind of work |
|
||||
| --- | --- |
|
||||
| `references/navigation-and-actions.md` | Navigation structure, action labeling and placement |
|
||||
| `references/forms.md` | Form design and validation UX |
|
||||
| `references/content-and-feedback.md` | Copy, loading/empty/error states, responsiveness |
|
||||
| `references/visual-and-accessibility.md` | Visual design, accessibility, responsive layout |
|
||||
| `references/tables-search-dialogs.md` | Data-dense views, search/filtering, dialogs/modals |
|
||||
| `references/destructive-and-error-prevention.md` | Destructive actions, error prevention, consistency, user control, progressive disclosure, perceived performance, defaults |
|
||||
Reference in new issue
Block a user