Julian lechnerandClaude Haiku 4.5
01220cebd4
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
30 lines
1.4 KiB
Markdown
30 lines
1.4 KiB
Markdown
## Navigation
|
|
|
|
* Navigation must be predictable and consistent.
|
|
* Users should always understand where they are.
|
|
* Users should always understand how to go back.
|
|
* Avoid hidden navigation when visible navigation is practical.
|
|
* Keep navigation depth shallow where possible.
|
|
* Use clear and descriptive navigation labels.
|
|
* Do not use ambiguous icons without labels when meaning is not obvious.
|
|
* Preserve navigation state when users return to a previous view where practical.
|
|
* Avoid resetting filters, search state or scroll position unnecessarily.
|
|
* Avoid unexpected redirects.
|
|
* Do not change navigation behavior between similar screens without a clear reason.
|
|
|
|
## Actions
|
|
|
|
* Use clear action labels.
|
|
* Prefer verbs that describe the actual outcome.
|
|
* Avoid vague labels such as `OK`, `Submit`, `Proceed` or `Execute` when a more specific label is possible.
|
|
* Make destructive actions clearly distinguishable.
|
|
* Keep dangerous actions away from common actions.
|
|
* Require confirmation for destructive or difficult-to-reverse actions.
|
|
* Do not require unnecessary confirmation for safe, reversible actions.
|
|
* Disable unavailable actions when the reason is obvious.
|
|
* Explain why an action is unavailable when it is not obvious.
|
|
* Avoid actions that appear clickable but are not.
|
|
* Provide immediate visual feedback after user actions.
|
|
* Prevent accidental duplicate submissions.
|
|
* Make loading, success and failure states visible.
|