interaction-design_skill

This skill helps you design intuitive user experiences with loading, error, empty states and accessible microinteractions.
  • TypeScript

52

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill secondsky/claude-skills --skill interaction-design

  • SKILL.md2.5 KB

Overview

This skill helps designers and developers create intuitive, accessible interaction experiences by prescribing feedback patterns, microinteractions, loading and error state treatments, and animation guidelines. It packages practical, production-ready patterns for web apps using modern stacks like React and Tailwind. Use it to standardize how UI responds to user input and system state across your product.

How this skill works

The skill inspects common interaction scenarios—button presses, loading flows, errors, empty states, and screen-reader announcements—and provides concrete implementations and timing guidance. It recommends durations for microinteractions and transitions, accessible ARIA patterns, skeleton loaders, error layouts with retry actions, and motion-respecting animation rules. Code snippets and rules-of-thumb make integration into React and TypeScript projects straightforward.

When to use it

  • Designing button/toggle feedback and microinteractions for touch or mouse
  • Implementing loading states and skeleton placeholders for slow network responses
  • Building error states with clear messages and retry/recovery flows
  • Creating meaningful empty states that guide the next user action
  • Setting animation timing and respecting prefers-reduced-motion for accessibility

Best practices

  • Provide immediate visual feedback for every user action to confirm intent
  • Show loading states for delays longer than ~0.5s using skeletons or spinners
  • Keep microinteractions short (100–200ms) and transitions under 500ms
  • Respect prefers-reduced-motion and ensure focus indicators remain visible
  • Include clear error text plus a recovery option (retry, help link, or contact)

Example use cases

  • Replace a static spinner with a skeleton loader and shimmer animation for content-heavy pages
  • Add a 150ms microinteraction to button presses to convey tactility on mobile
  • Implement an ErrorState component with role="alert" and a retry callback for failed API calls
  • Create an EmptyState component that suggests the next action and includes a primary CTA
  • Announce important status changes to screen readers using an aria-live StatusAnnouncer

FAQ

Use 100–200ms for microinteractions, 200–400ms for transitions, and 300–500ms for entrances; keep most animations under 500ms.

How do I handle users who prefer reduced motion?

Detect prefers-reduced-motion and disable or simplify nonessential animations, while preserving meaningful state changes and focus outlines.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational