micro-interactions

A design and engineering guide for small interface responses such as transitions, loading indicators, swipe feedback, and haptics. It covers mobile apps, web apps, and responsive websites.

In plain words
What is it for?
Use it to design, implement, review, or improve the feedback users receive after taps, hovers, scrolling, gestures, voice input, and system events.
Why use it?
It helps make interactions understandable and responsive while considering behavior, performance, and accessibility.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/solinkz/micro-interactions-skill/micro-interactions
Any agent
npx skills add solinkz/micro-interactions-skill --skill micro-interactions
Clone the repo
git clone --depth 1 https://github.com/solinkz/micro-interactions-skill

Made for: Claude Code, Codex.

Per session 293 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,762 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00293 $0.05762
Opus 5 $0.00147 $0.02881
Sonnet 5 $0.00059 $0.01152
Haiku 4.5 $0.00029 $0.00576

Measured 3d ago against content hash 65fe325d9213, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

micro-interactions scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/micro-interactions/SKILL.md · 569 lines

How it starts

The opening of the file, as written. The whole thing — 569 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Micro-Interaction Architect

You are a micro-interaction architect — an expert who understands the science, psychology, and craft behind every small interaction that makes digital products feel alive. You work across all platforms: iOS, Android, React Native, web (React/Vue/Svelte/vanilla), and responsive websites. You think in triggers, feedback loops, easing curves, and spring physics.

Your role is to design, implement, audit, and consult on micro-interactions that are functional, performant, accessible, and delightful.


Core Framework: Dan Saffer's 4-Part Model

Apply this to EVERY micro-interaction you design or review:

TRIGGER → RULES → FEEDBACK → LOOPS & MODES
  1. Trigger — What initiates it? (tap, hover, scroll, system event, gesture, voice)
  2. Rules — What happens? What's the logic? What's allowed/disallowed during the interaction?
  3. Feedback — How does the user know it worked? (visual, auditory, haptic, or multi-sensory)
  4. Loops & Modes — Does it repeat? Does it change over time? Does context alter behavior?

Always explicitly state these four parts when designing a new micro-interaction.


Decision Framework

Before adding any micro-interaction, run this checklist:

1. Does this action need confirmation?          → ADD feedback animation
2. Is something loading or processing?           → ADD progress/skeleton/shimmer
3. Is there a state change?                      → ANIMATE the transition
4. Could the user miss something important?      → ADD attention-drawing motion
5. Is this a frequent/repeated action?           → BE SUBTLE — don't annoy
6. Is this purely decorative?                    → SKIP unless brand demands it
7. Does it work without animation?               → GOOD — animation enhances, never required
8. Would this frustrate on the 100th use?        → TONE IT DOWN or remove

Platform Detection & Adaptation

ALWAYS determine the target platform(s) first. Different platforms demand different approaches:

Read the full file on GitHub · 569 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 569 lines · 293 tokens per session scan A 65fe325d9213

Subscribe to this mod's changes

micro-interactions is a skill published in the GitHub repository solinkz/micro-interactions-skill (10 stars, last pushed 5mo ago), licensed MIT. It adds 293 tokens to every session and 5,762 once invoked, about $0.0015 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

animation-designer

Expert in web animations, transitions, and motion design using Framer Motion and CSS.

daffy0208/ai-dev-standards · 20 tokens

brand-visual-language

A brand's visual tone — playful or serious, rounded or angular — should be consistent across all UI elements. Shape language in typography, border-radius, and iconography communicates personality before a single word is read. Use when establishing a design system, choosing icon libraries, setting border-radius tokens…

dembrandt/dembrandt-skills · 68 tokens

micro-interactions

Micro-interactions are small, purposeful animations and responses that reward the user and make the interface feel alive — an animated icon, a satisfying toggle, a subtle reveal. Borrowed from the natural world, they add delight without distraction. Use when designing interactive components, success states, toggles…

dembrandt/dembrandt-skills · 70 tokens

elevation-and-depth

Elevation — subtle shadows and layering — communicates visual hierarchy by lifting elements above the surface. Combined with border-radius, it creates the tactile quality of cards, modals, and interactive surfaces. Use when designing cards, dropdowns, modals, tooltips, or any floating UI element.

dembrandt/dembrandt-skills · 62 tokens

loading-states-and-perceived-performance

Manage user expectations during wait times with appropriate loading states — from simple spinners to complex skeleton screens and staggered animations. Perceived performance is often more important than actual load time. Use when designing data-heavy components, handling API calls, building hero sections, or improving…

dembrandt/dembrandt-skills · 68 tokens

motion-and-storytelling

Disney's 12 animation principles, cinematic storytelling techniques, and comic book conventions apply to web UI — used subtly, they make interfaces feel alive, intentional, and emotionally resonant. Use when designing transitions, micro-interactions, onboarding flows, scroll animations, or any motion in the UI.

dembrandt/dembrandt-skills · 63 tokens