AGENT SKILL

micro-interaction-spec

Specify one micro-interaction completely — trigger, rules, feedback, loops, and modes. Use when handing a single interaction to engineering. For motion craft alone use `animation-principles`; for multi-state components use `interaction-state-machine`.

License 许可
MIT
最近更新
2026-11-04
Stars
★ 0
Forks
0

01 前言 Front Matter

name
micro-interaction-spec
description
Specify one micro-interaction completely — trigger, rules, feedback, loops, and modes. Use when handing a single interaction to engineering. For motion craft alone use `animation-principles`; for multi-state components use `interaction-state-machine`.
disable-model-invocation
true

02 资源文件 3

03 SKILL.md 正文

Micro-Interaction Spec

You are an expert in designing micro-interactions that make interfaces feel alive and intuitive.

What You Do

You specify micro-interactions using a structured framework covering trigger, rules, feedback, and loops.

Micro-Interaction Framework

1. Trigger

What initiates the interaction: user action (click, hover, swipe), system event (notification, completion), or conditional (time-based, threshold).

2. Rules

What happens once triggered: the logic and sequence of the interaction, conditions and branching.

3. Feedback

How the user perceives the result: visual change (color, size, position), motion (animation, transition), audio (click, chime), haptic (vibration patterns).

4. Loops and Modes

Does the interaction repeat? Does it change over time? First-time vs repeat behavior, progressive disclosure.

Common Micro-Interactions

  • Toggle switches with state animation
  • Pull-to-refresh with progress indication
  • Like/favorite with celebratory animation
  • Form validation with inline feedback
  • Button press with depth/scale response
  • Swipe actions with threshold feedback
  • Long-press with radial progress

Specification Format

For each micro-interaction: name, trigger, rules (sequence), feedback (visual/audio/haptic), duration/easing, loop behavior, accessibility considerations.

Best Practices

  • Every micro-interaction should have a purpose
  • Keep durations short (100-500ms for most)
  • Provide immediate feedback for user actions
  • Respect reduced-motion preferences
  • Test on target devices for performance

04 同仓库更多 Skills

jorgesolerrr
jorgesolerrr/skills

explainroo

Make an explainer video (MP4) with a voice-over using explainroo. The voice is made on this computer and no API key is needed. Use when the user asks for an explainer, how-to, walkthrough, launch or tutorial video, an animated diagram with a voice-over, or a short for YouTube, Reels or TikTok.

★ 0
jorgesolerrr
jorgesolerrr/skills

unslop

Cut AI tells from prose a human will read. Use when drafting or editing docs, READMEs, PR descriptions, commit messages, emails or posts, or when the user says unslop or "sounds like AI".

★ 0
jorgesolerrr
jorgesolerrr/skills

technical-writing

Layered technical-writing standard (Diátaxis, Google style, STE, Global English) for docs, RFCs, READMEs, PR descriptions and commit messages.

★ 0
jorgesolerrr
jorgesolerrr/skills

no-comments

Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.

★ 0
jorgesolerrr
jorgesolerrr/skills

ponytail

Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.

★ 0
jorgesolerrr
jorgesolerrr/skills

ponytail-review

Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.

★ 0