/stark-usability

/stark-usability

Use this command when a generated UI looks attractive but might fail real use.

Inputs

• Product/screen:
• User mode:
• Core task:
• Frequency:
• Risk:
• Existing UI or plan:

Output

Task ergonomics contract
- Core task:
- User mode:
- Frequency:
- Risk:
- Success metric:
- Cognitive load:
- Control model:
- Speed path:
- Error prevention:
- Recovery:
- State matrix:
- Evidence plan:

Usability findings
- Hard fails:
- Highest-impact repair:
- What visual design must preserve:

Use `references/ux-patterns/task-ergonomics.md` first, then `references/ui-patterns/interaction-state-matrix.md` for concrete state behavior. If a contextual pattern applies, also use the matching brief in `references/ux-patterns/`.