Skip to main content
reopt Handbook
reopt Handbook
Design Systems for the AI Era

Foundation

Token ArchitectureComponent SpecBuilt-in Accessibility

AI Workflow

Prompt InterfaceDESIGN.md InterfaceAgentic Design Quality ControlWorkflow StrategiesAI-Based Design System EvolutionContext Injection

User Experience

Consistency PatternsInteraction DesignForms and Data Input

Next Interfaces

Agent UI ProtocolsGenerative UISpatial and Multimodal Interfaces

Practice

Execution PlaybookMigration StrategyGovernance and CollaborationCase Studies

Operations

Verification ChecklistUpdate Log
Handbook›Design Systems for the AI Era›Interaction Design
한국어English

Interaction Design

Tokenize state feedback, microinteractions, and motion behavior.

Key takeaways

  • Interaction quality lives in the details, so hover, focus, pressed, loading, disabled, error, and success states belong in the component contract.
  • Motion should be tokenized for duration and easing so agents reuse named values instead of arbitrary timings.
  • Hover, focus, and loading states must never change component dimensions, and motion must clarify state rather than decorate.
  • Respect reduced-motion preferences and never animate critical information in a way that hides it.
  • Verify with a keyboard-only pass, a reduced-motion pass, loading/disabled screenshots, and a no-layout-shift check on hover and focus.

Interaction quality is determined by details: focus, hover, pressed, loading, disabled, error, success, and transition states. Agents need these states defined as part of the component contract.

Interaction State Matrix

StateRequired behavior
HoverVisual affordance without layout shift.
FocusVisible focus ring and keyboard support.
PressedImmediate feedback for action controls.
LoadingPrevent duplicate work and preserve layout.
DisabledCommunicate unavailable action and reason when needed.
ErrorTie visual message to accessible announcement.
SuccessConfirm completion without blocking flow.

Motion Tokens

export const motion = {
  duration: {
    instant: '80ms',
    fast: '150ms',
    normal: '220ms',
  },
  easing: {
    standard: 'cubic-bezier(0.2, 0, 0, 1)',
    emphasized: 'cubic-bezier(0.2, 0, 0, 1.2)',
  },
}

Agent Rules

  1. Motion must clarify state, not decorate the page.
  2. Hover, focus, and loading states cannot change component dimensions.
  3. Respect reduced-motion preferences.
  4. Do not animate critical information in a way that hides it.
  5. Keep complex animation inside tested primitives.

Verification

  • Keyboard-only interaction pass.
  • Reduced-motion pass.
  • Loading and disabled state screenshots.
  • No layout shift on hover or focus.

Related docs

Built-in Accessibility

Design components so AI automatically generates accessible UI.

Component Spec

Component schemas that AI can interpret and generate accurately.

Cmd. /focus

Claude Code Command Master · Changes the visible focus area in fullscreen rendering.

Scenario: Frontend Team

Harness Engineering · Design a harness where browser QA, accessibility, visual state, and design rules are load-bearing.

React 19.2 Concurrency Patterns

Expo Enterprise Production · Mobile patterns for transitions, Suspense, and route-level loading in Expo SDK 56.

Consistency Patterns

System design for visual and structural consistency in AI-generated UI.

Forms and Data Input

Standardize validation, errors, and complex form composition.

On this page

Interaction State MatrixMotion TokensAgent RulesVerification