microinteractions

Design triggers, rules, feedback, and loops for UI microinteractions using Dan Saffer's framework.

Updated Jun 27, 2026
One-click install
npx skills add https://github.com/rachmadideni/ai-staff-assistant --skill microinteractions-rachmadideni
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: microinteractions
Source: https://github.com/rachmadideni/ai-staff-assistant/tree/main/.agents/skills/microinteractions
Command: npx skills add https://github.com/rachmadideni/ai-staff-assistant --skill microinteractions-rachmadideni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Interfaces often feel dead or untrustworthy because small interaction details -- button feedback, loading states, toggles, form validation -- are underdesigned. This Skill provides a structured framework for auditing and designing these microinteractions so every interactive moment has a clear trigger, predictable rules, immediate feedback, and thoughtful long-term behavior. ## Core Features & Use Cases - Four-Part Structure: Design any microinteraction using Trigger, Rules, Feedback, and Loops & Modes, with scoring against a 10/10 quality rubric. - Detailed Case Studies: Reference implementations for form submission, toggles, pull-to-refresh, loading states, and toast notifications, including animation specs, accessibility requirements, and edge cases. - Signature Moments: Guidance on creating distinctive, brand-defining interactions like Stripe's payment checkmark or Slack's loading messages. - Use Case: When a user says "the interface feels dead" or asks to polish a form's validation feedback, apply the framework to map every state (idle, active, success, error), define feedback timing under 100ms, and add progressive reduction for returning users. ## Quick Start Audit the submit button and form validation flow in my settings page using the microinteractions framework and tell me the current score and what is needed to reach 10/10.

Frequently Asked Questions about microinteractions

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

FAQPage Schema
How do I design microinteractions for a UI?▼

Use Dan Saffer's four-part structure: define a Trigger that initiates the interaction, Rules that determine what happens, Feedback that shows what is happening, and Loops & Modes that govern long-term behavior. Score the result against a 10/10 rubric and fix gaps in each part.

What is the right feedback timing for button clicks and loading states?▼

Direct manipulation feedback should appear within 100ms to feel instantaneous. For operations over 300ms show an inline spinner, over 1 second use a skeleton screen, and over 5 seconds use a determinate progress bar with percentage.

How do I make a toggle switch accessible?▼

Use role="switch" with aria-checked, support Space bar toggling, provide a visible focus indicator, and respect reduced-motion settings by skipping the slide animation. Ensure the touch target is at least 44x44pt and never rely on color alone to show state.

When should I use optimistic UI versus waiting for server confirmation?▼

Use optimistic UI when the action succeeds over 99% of the time, is low-stakes, and can be reverted cleanly, such as likes or toggles. Avoid it for irreversible or high-stakes actions like payments, where a false success state would erode trust.

What are the limitations of using modes in interface design?▼

Modes cause mode errors where the same action produces different results based on hidden state. Minimize modes to two or fewer, make the current mode highly visible with banners or color coding, and prefer spring-loaded quasi-modes that exit when the trigger is released.