updated context documents
This commit is contained in:
@@ -135,3 +135,45 @@ Avoid:
|
||||
- dashboard-style density.
|
||||
|
||||
The next question should be the strongest visual element.
|
||||
|
||||
## TL;DR Workspace Rules
|
||||
|
||||
The newest state is the most important state.
|
||||
|
||||
The primary focus of every screen should be the user's next action, not the history of how they arrived there.
|
||||
|
||||
### Information hierarchy
|
||||
|
||||
1. Current investigation
|
||||
2. Why this matters
|
||||
3. Response
|
||||
4. Current understanding
|
||||
5. Investigation history
|
||||
6. Original situation
|
||||
7. Developer details
|
||||
|
||||
### Progressive disclosure
|
||||
|
||||
Show only the information needed for the current decision.
|
||||
|
||||
Everything else should be collapsible or secondary.
|
||||
|
||||
### Cognitive load
|
||||
|
||||
The user should never need to scan an entire page to discover:
|
||||
|
||||
- what is happening
|
||||
- what they need to do next
|
||||
- why they are being asked
|
||||
|
||||
These should always be immediately visible.
|
||||
|
||||
### Investigation history
|
||||
|
||||
History exists to provide confidence and traceability, not to compete with the current investigation.
|
||||
|
||||
History should remain collapsed unless the user chooses to inspect previous reasoning.
|
||||
|
||||
### Original situation
|
||||
|
||||
Once an investigation has started, the original scenario becomes reference material rather than the primary focus.
|
||||
|
||||
Reference in New Issue
Block a user