Back to Skills

interaction-design

verified

Design user interactions, flows, and interface behaviors. Use for wireframes, prototypes, micro-interactions, user flows, state machines, affordance design, and usability reviews. Covers IxD principles, Nielsen heuristics, Fitts's Law, Hick's Law, and emerging paradigms (spatial, conversational, gesture-based interfaces). Keywords: IxD, wireframe, prototype, user flow, micro-interaction, UI state diagram, screen flow, clickable prototype, interaction pattern.

View on GitHub

Marketplace

teslasoft-skills

teslasoft-de/claude-skills-marketplace

Plugin

ux

design

Repository

teslasoft-de/claude-skills-marketplace

plugins/ux/skills/interaction-design/SKILL.md

Last Verified

January 25, 2026

Install Skill

Select agents to install to:

Scope:
npx add-skill https://github.com/teslasoft-de/claude-skills-marketplace/blob/main/plugins/ux/skills/interaction-design/SKILL.md -a claude-code --skill interaction-design

Installation paths:

Claude
.claude/skills/interaction-design/
Powered by add-skill CLI

Instructions

# Interaction Design (IxD) Skill

Design interactive digital products with a focus on **how users engage with interfaces**. IxD bridges user needs and system capabilities through controls, feedback, and information flows.

## When to Use

- Designing user flows for features or complete products
- Creating wireframes at any fidelity level
- Building interactive prototypes for validation
- Defining micro-interactions and feedback patterns
- Documenting UI component state machines
- Reviewing interfaces against usability heuristics
- Designing for emerging paradigms (spatial, conversational, gesture)

## When NOT to Use

- Pure user research (use UX research methods)
- Visual design/styling only (use UI design patterns)
- Brand identity work (use branding guidelines)
- Marketing copywriting (use content strategy)
- Accessibility audits only (use WCAG checklist)

---

## Quick Start (Happy Path)

1. **Define the goal** - What task should users complete?
2. **Map the flow** - Sketch entry points, decisions, and outcomes
3. **Wireframe key screens** - Low-fi layout with content hierarchy
4. **Add interactions** - Micro-interactions, transitions, feedback
5. **Document states** - All possible UI component states
6. **Validate** - Check against Nielsen heuristics
7. **Prototype** - Build clickable prototype for testing

---

## Core Procedure

### Phase 1: Research & Define

```yaml
inputs:
  - User goals and context
  - Business requirements
  - Technical constraints

outputs:
  - User flow diagram
  - Key screen list
  - Interaction requirements
```

**Steps:**
1. Identify primary user task (happy path)
2. Map entry points and exit points
3. Define decision branches and error states
4. List screens/views required
5. Document edge cases

### Phase 2: Design & Wireframe

```yaml
fidelity_levels:
  sketch: Quick paper drawings for ideation
  low_fi: Basic shapes, grayscale, placeholder content
  mid_fi: More detail, basic interactions noted
  high_fi: Near-final layout with 

Validation Details

Front Matter
Required Fields
Valid Name Format
Valid Description
Has Sections
Allowed Tools
Instruction Length:
8168 chars