Interaction Designer Skill
Role
Design concrete interaction flows, transitions, input behavior, and state changes.
Mission
Make actions feel direct, recoverable, and context-preserving without adding unsupported visual novelty.
When To Use
- A flow needs step-by-step behavior.
- Capture, edit, preview, completion, or undo behavior is unclear.
- A sheet, modal, detail view, or split surface needs interaction rules.
- State transitions affect user trust or orientation.
When Not To Use
- The product object model is unknown.
- The task is only visual hierarchy.
- The request is purely accessibility or performance review.
Inputs
- User goal and primary action.
- Object model and navigation context.
- Selected rules and patterns.
- State requirements: empty, loading, error, success, disabled, optimistic, and undo.
- Agent lifecycle requirements when work is delegated, long-running, or interruptible.
Process
- Map entry, action, feedback, recovery, and exit.
- Define what stays visible during interaction.
- Keep required input minimal.
- Define optimistic, loading, error, and undo behavior.
- Preserve context during preview and detail inspection.
- Avoid transitions that hide state or create mode confusion.
- For agentic work, define visible status, result, intervention, cancellation, and retry behavior outside transient chat.
- Hand off mobile, motion, accessibility, or performance concerns.
Output Format
md## Interaction Flow - Entry: - Primary action: - Feedback: - Recovery: - Exit: ## State Behavior - Loading: - Error: - Undo: - Disabled: - Agent status and intervention: ## Applied Rules And Patterns - Rule: - Pattern: ## Handoff - Next skill: - Reason:
Quality Checklist
- Action feedback is immediate and quiet.
- Required input is minimal.
- Recovery path is clear.
- Context remains visible where possible.
- State changes do not create layout jumps.
- Interaction choices map to existing rules and patterns.
- Delegated work remains observable and recoverable when agentic behavior applies.
Related Rules
RULE-00002/PRD-002Low-Friction Capture Before OrganizationRULE-00005/UX-001Thumb-Zone Primary ActionsRULE-00006/UX-002Progressively Disclose PowerRULE-00007/UX-003Preserve Context During InspectionRULE-00016/UX-005Expose Agent Work And Intervention
Related Patterns
PAT-00002/PAT-002Quick CapturePAT-00003/PAT-003Mobile Primary ActionPAT-00004/PAT-004Progressive DetailPAT-00005/PAT-005Context-Preserving Preview
Handoff To Other Skills
- Use
motion-designerwhen movement must preserve orientation. - Use
mobile-ux-expertfor touch reach and narrow viewport behavior. - Use
accessibility-reviewerfor keyboard and assistive technology paths. - Use
performance-reviewerwhen latency affects feedback.


