ui-designer/interaction-specification

Defines UI interaction specifications covering loading states, empty states, feedback, animations, and accessibility.

553|50|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/echoVic/boss-skill --skill ui-designer-interaction-specification
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ui-designer/interaction-specification
Source: https://github.com/echoVic/boss-skill/tree/main/skill/skills/ui-designer/interaction-specification
Command: npx skills add https://github.com/echoVic/boss-skill --skill ui-designer-interaction-specification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design teams often ship interfaces with inconsistent loading indicators, unhelpful empty states, missing feedback, and poor accessibility. This Skill provides a complete interaction specification so every UI design document covers these details consistently.

Core Features & Use Cases

  • Loading & Empty States: Standardized patterns for skeleton screens, spinners, no-data, no-result, error, and 404 scenarios with clear user guidance.
  • Feedback & Motion: Specifications for Toast notifications, confirmation modals, form validation timing, page transitions, and micro-interactions with exact durations and easing values.
  • Accessibility Compliance: WCAG AA contrast ratios, keyboard navigation mappings, ARIA attributes for screen readers, and minimum touch target sizes.
  • Use Case: When a UI designer agent produces a design document for a new dashboard, this Skill ensures the output includes a full interaction specification section covering responsive breakpoints and mobile gestures like pull-to-refresh and swipe-to-delete.

Quick Start

Ask the UI designer agent to generate the interaction specification section for your interface design document, covering loading states, feedback, animations, and accessibility.

Frequently Asked Questions about ui-designer/interaction-specification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define loading states in a UI design specification?▼

Map each loading scenario to a pattern: skeleton screens for first page loads, top progress bars for refreshes, in-button spinners for form submissions, and bottom spinners for infinite scroll. Skeleton screens should mimic real content layout with gray placeholder blocks and a subtle shimmer animation.

What should an empty state design include?▼

An empty state should include a friendly illustration or icon, an explanation of why the view is empty, and a clear call-to-action guiding the next step, such as a create button for no-data views or a retry button for network errors. Never leave users without direction.

What color contrast ratio meets WCAG AA accessibility standards?▼

WCAG AA requires at least 4.5:1 contrast for body text, 3:1 for large text of 18px or more, and 3:1 for icons and UI components. Verify each text and background color combination against these thresholds before finalizing a design.

How long should UI animation durations be?▼

Micro-interactions like button hovers should run around 100-150ms, while larger transitions such as page fades and modal appearances can take 200-300ms. Keep animations purposeful and restrained, and respect user preferences for reduced motion.

What is the minimum touch target size for mobile interfaces?▼

Mobile touch targets should be at least 44x44px, with 48x48px recommended, while desktop targets can be 32x32px minimum. Maintain at least 8px spacing between adjacent interactive elements to prevent mis-taps.