agentleFS
juandelossantosjuandelossantos/another-agent-skills/skills/delight-skill/SKILL.md

delight-skill

Skill1 starsChanged 11 days agoMITView on GitHub

Add micro-interactions, transitions, hover states, and feedback animations. Use when UX feels stiff or lifeless. Do NOT use for functional or utility UIs.

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No feedback on hover, tap, or action completion

    line 27
  2. Distinctive:

    After functionality is complete, before polish

    line 31
  3. Distinctive:

    Every user interaction is a delight opportunity:

    line 49
  4. Distinctive:

    Keep durations between 150ms-400ms (below 150ms is instant, above 400ms is slow)

    line 104
  5. Very specific:

    Use will-change: transform on animated elements

    line 105
  6. Distinctive:

    Avoid animating 10+ elements simultaneously

    line 107

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Delight Skill

Add micro-interactions so interfaces respond like physical things.

→ See guides/ANIMATIONS-GUIDE.md for animation principles and types. → See guides/IMPLEMENTATION-GUIDE.md for code examples and patterns.

Micro-interactions are the difference between a UI that feels alive and one that feels like a PDF. Every interaction should leave a trace.

When to Use

  • Interface feels stiff or lifeless
  • No feedback on hover, tap, or action completion
  • User says "make it feel more responsive"
  • Transitions feel jarring or instant (no duration)
  • Loading states are blank or flicker
  • After functionality is complete, before polish

When NOT to Use

  • Performance optimization (use optimize — then delight on top)
  • Structural changes (use build skills)
  • Replacing missing states (use harden first)

Output Contract

ArtifactFormatLocationQuality Criteria
Micro-interaction CSSCSS/animationsComponent source files150-400ms, only transform/opacity, reduced-motion fallback

Process

1. Identify Touchpoints

Every user interaction is a delight opportunity:

InteractionCurrent stateDelight opportunity
HoverStaticScale, glow, shadow lift
Tap/clickInstantRipple, micro-bounce, color shift
State changeAbruptSmooth transition, morph
LoadingSpinner or blankSkeleton, progress bar, shimmer
SuccessNothingCheckmark, confetti, subtle pulse
ErrorRed flashShake, gentle wiggle
EmptyBlankAnimated illustration, subtle float
Page enterInstantFade in, slide, stagger children

2. Fix by Category

Hover & Focus

BeforeAfterDuration
No hover effecttransform: scale(1.03) + shadow lift150-200ms
Instant color swapbackground-color transition200-300ms on button
No focus ringoutline with transition150ms
Card hover nonetranslateY(-2px) + subtle shadow200ms ease

Tap & Click

BeforeAfterNotes
Instant jumptransform: scale(0.97) on activeReturns on release
No feedbackButton darkens 10% on pressApply to all interactive
Toggle instantSwipe + morph animation250ms spring

State Transitions

BeforeAfterDuration
Content appears (pop in)Fade + slide up 8px200-300ms
Content disappearsFade + scale down150-200ms
Page enters instantlyStagger children, fade up300ms total
Modal opens instantlyScale from 0.95 + backdrop fade200ms
Tab switch instantSlide content directionally200ms

Loading & Feedback

BeforeAfterNotes
Blank while loadingSkeleton screen (pulse animation)Match shape
Spinner onlyProgress bar with known durationOr shimmer for unknown
Success no feedbackCheckmark draw animation300ms
Error no feedbackShake input + highlight border300ms shake
Toast appears instantlySlide in from top/right + fade250ms + 3s auto-dismiss

3. Performance Rules

  • Animate ONLY transform and opacity — never width, height, top, left
  • Keep durations between 150ms-400ms (below 150ms is instant, above 400ms is slow)
  • Use will-change: transform on animated elements
  • Respect prefers-reduced-motion (use harden to add it)
  • Avoid animating 10+ elements simultaneously

4. Output Format

/delight the product card

Fix 1: Hover state
  - Before: no hover effect
  - After: transform: scale(1.02), box-shadow: 0 4px 12px, transition: 200ms

Fix 2: Add to cart button
  - Before: text changes instantly
  - After: icon morphs from "+" to checkmark (200ms), button pulses green

Fix 3: Card enter animation
  - Before: all cards appear at once
  - After: stagger in by index, translateY(20px) → translateY(0), 250ms each

Fix 4: Loading skeleton
  - Before: loading text
  - After: card-shaped skeleton with shimmer animation

5. Escalation Rules

FindingEscalate to
Animation causes jankoptimize first, then reapply
Need complex gestureInteraction design review
Animation contradicts brandDesign decision

Pitfalls

  • Over-delighting — Not every pixel needs to animate. Animate interactions, not eye candy.
  • Accessibility first — Always test with prefers-reduced-motion. Delight must degrade gracefully.
  • Duration drift — Keep all micro-interactions within 150-400ms. Faster than conscious thought.
  • Animation without purpose — Every animation should communicate: this changed, this is interactive, this is happening.

QA Gates

  • All interactive elements have hover/focus feedback
  • All state changes have transitions (not instant)
  • All durations within 150-400ms
  • Only transform and opacity animated
  • prefers-reduced-motion respected
  • Loading states have animation (not blank)
  • Success/error feedback is animated
  • Page enters have subtle transition
  • No animation for animation's sake

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.