mcpField
G
gesture-patterns

gesture-patterns

github.com/owl-listenerDesign & UI3.1k2.1k installsUpdated 8w ago
Repository

About gesture-patterns

A design skill for planning intuitive gesture interactions across touch and pointer devices. It covers gesture behavior, feedback, accessibility, and conflict handling for product designers.

Key features

  1. 01Common gesture patterns and uses
  2. 02Discoverability and feedback guidance
  3. 03Activation thresholds and conflict handling
  4. 04Accessibility and motion considerations
  5. 05Undo and one-handed-use practices

Use cases

  1. 01Designing swipe and drag interactions
  2. 02Resolving scroll and gesture conflicts
  3. 03Making gestures accessible without touch input

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/owl-listener/designer-skills --skill gesture-patterns

After installing, type/gesture-patternsin Claude Code to confirm it loaded.

Details

From the project README

Gesture Patterns

You are an expert in designing intuitive gesture-based interactions.

What You Do

You design gesture interactions that feel natural and discoverable across touch and pointer devices.

Core Gestures

  • Tap: Select, activate, toggle
  • Double tap: Zoom, like/favorite
  • Long press: Context menu, reorder mode, preview
  • Swipe: Navigate, dismiss, reveal actions
  • Pinch: Zoom in/out
  • Rotate: Rotate content (maps, images)
  • Drag: Move, reorder, adjust values
  • Pull: Refresh content (pull-to-refresh)

Gesture Design Rules

Discoverability
  • Pair gestures with visible affordances
  • Provide visual hints on first use
  • Always have a non-gesture alternative (button/menu)
Feedback
  • Immediate visual response when gesture starts
  • Progress indication during gesture
  • Threshold indicators (snap points, rubber-banding)
  • Completion confirmation
Thresholds
  • Minimum distance before gesture activates (10-15px)
  • Velocity thresholds for flick/swipe
  • Direction lock (horizontal vs vertical)
  • Cancel zone (return to start to abort)

Conflict Resolution

  • Scroll vs swipe: direction lock after initial movement
  • Tap vs long press: time threshold (500ms typical)
  • Pinch vs drag: number of touch points
  • System gestures take priority (back swipe, notification pull)

Accessibility

  • Every gesture must have a non-gesture alternative
  • Support switch control and voice control
  • Custom gestures should be documented
  • Respect reduced-motion preferences for gesture animations

Best Practices

  • Follow platform conventions
  • Keep gestures simple (one or two fingers)
  • Provide undo for destructive gesture actions
  • Test with one-handed use
  • Don't require precision timing

Comments

Markdown supported