microinteractions

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

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/trobias/portfolio-nextjs-v2 --skill microinteractions-trobias
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: microinteractions
Source: https://github.com/trobias/portfolio-nextjs-v2/tree/main/.agents/skills/microinteractions
Command: npx skills add https://github.com/trobias/portfolio-nextjs-v2 --skill microinteractions-trobias

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, validation responses — are missing or inconsistent. This Skill provides a structured framework to design, audit, and score those contained product moments so users always know what is happening. ## Core Features & Use Cases - Four-Part Design Framework: Design any microinteraction through Trigger, Rules, Feedback, and Loops & Modes, with ethical boundaries for each part. - Diagnostic Scoring: Audit an existing interaction against an 8-row checklist and compute a 0-10 score with specific fixes for each failed row. - 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. - Use Case: When a user says a form feels unresponsive, apply the framework to add sub-100ms inline validation feedback, a submitting state on the button, and an error recovery pattern that preserves input. ## Quick Start Ask the assistant to audit the loading state of your app's submit button using the microinteractions framework and score it against the quick diagnostic.

Frequently Asked Questions about microinteractions

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

FAQPage Schema
How do I design better microinteractions for my app?▼

Break the interaction into four parts: a trigger that initiates it, rules that define what happens, feedback that shows what is happening, and loops and modes that govern long-term behavior. Then audit it against the eight-row diagnostic checklist to find gaps.

What is the four-part microinteraction framework?▼

It is Dan Saffer's structure from the book Microinteractions: Trigger, Rules, Feedback, and Loops & Modes. Every contained product moment, from a toggle to pull-to-refresh, can be designed and evaluated through these four parts.

How fast should UI feedback be after a user action?▼

Feedback for direct manipulation should appear within 100ms to feel instantaneous. Delays of 300ms to 1s need a spinner or transition, and operations over 5 seconds need a determinate progress indicator.

When should I use a skeleton screen instead of a spinner?▼

Use a skeleton screen when loading takes 1 to 5 seconds and the final layout is known, since it reduces perceived wait time. Use a spinner for shorter waits under 1 second and a determinate progress bar for operations over 5 seconds.

Why do mode errors happen in interface design?▼

Mode errors occur when the same action produces different results depending on a hidden state, such as typing with Caps Lock on. Prevent them by making the current mode highly visible, minimizing mode count, or using spring-loaded quasi-modes.

What are the limitations of gesture-based triggers like pull-to-refresh?▼

Gesture triggers have no visible affordance, so users may never discover them. Pair them with a visible fallback such as a refresh button, and use a long loop that shows a hint for the first few uses before removing it.