saranskumar Goal
Define interaction behavior that is consistent, clear, and easy to hand off to implementation.
When to Use
- User flows exist but interaction details are missing.
- A screen or component has meaningful state changes.
- Validation, confirmation, or async feedback needs definition.
Instructions
- Identify the trigger action and affected UI states.
- Define immediate feedback, async feedback, and recovery behavior.
- Clarify validation timing, confirmations, and destructive action patterns.
- Tie interaction behavior to accessibility and responsive needs.
Constraints
- Do not describe animation for its own sake.
- Keep interactions legible to engineering.
- Avoid unnecessary mode or step changes.
Output Format
- interaction summary
- event/state transitions
- feedback behavior
- accessibility notes
Examples
- "Design the interaction behavior for this multi-step form."
- "How should inline editing work here?"