Ajouter des moments de joie aux interfaces

VérifiéSûr

Transformez les interfaces fonctionnelles en expériences mémorables en ajoutant des micro-interactions, des surprises et des touches personnalisées.

Spar Skills Guide Bot
DeveloppementIntermédiaire
06/08/2026
Claude CodeCursorWindsurf
#frontend#micro-interactions#animation#ui-design#ux

Recommandé pour

Synthèse automatique

Guide pour repérer et ajouter des micro-interactions, animations et touches de personnalité qui rendent une interface mémorable sans gêner l'usage.

Points forts

  • Cadre explicite pour choisir les bons moments (succès, états vides, chargement, erreurs, easter eggs).
  • Principes anti-abus clairs : delight en moins d'une seconde, jamais bloquant, toujours skippable.
  • Extraits CSS concrets (états de bouton, easing ease-out-quart) directement réutilisables.
  • Rappelle d'adapter le ton au domaine et à l'audience (banque ≠ jeu vidéo).

Limites

  • S'appuie sur les commandes externes /frontend-design et /teach-impeccable, non fournies ici.
  • Le document est tronqué (section « Loading delight » inachevée) et reste très orienté CSS.
  • Aucune méthode pour mesurer ou tester l'impact réel du delight sur les utilisateurs.
Quand l'utiliser

Quand une interface fonctionnelle doit gagner en personnalité et en polissage (micro-interactions, états de succès, onboarding).

Quand l'éviter

À éviter sur des interfaces critiques ou très réglementées où un effet ludique peut distraire ou entamer la confiance.

Analyse de sécurité

Sûr
Score qualité80/100

This is a purely editorial frontend/UX design skill. It contains only prose guidance and illustrative CSS/HTML snippet examples for micro-interactions, copy tone, and animations. There are no shell commands, no network calls, no file writes, no credential handling, and no obfuscated payloads. The only mild note is that it hard-depends on sibling skills (/frontend-design, /teach-impeccable) that are not bundled here, which is a dependency/portability concern rather than a security one.

Aucun point d'attention détecté

Comment cette analyse est faite

Exemples

Polish a pricing page
Add delight to our SaaS pricing page: make the plan cards feel satisfying on hover and give the post-signup success state some personality, but keep it professional for a B2B audience.
Friendlier empty state
Our dashboard empty state is boring. Add a subtle, playful animation and a friendly message that fits our brand, without slowing anything down.
Streak celebration
Add a small celebration when a user hits a 7-day streak — under a second, respects prefers-reduced-motion, and doesn't block the next action.

name: delight description: Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful. Use when the user asks to add polish, personality, animations, micro-interactions, delight, or make an interface feel fun or memorable. user-invocable: true argument-hint: "[target]"

Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences.

MANDATORY PREPARATION

Invoke /frontend-design — it contains design principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first. Additionally gather: what's appropriate for the domain (playful vs professional vs quirky vs elegant).


Assess Delight Opportunities

Identify where delight would enhance (not distract from) the experience:

  1. Find natural delight moments:

    • Success states: Completed actions (save, send, publish)
    • Empty states: First-time experiences, onboarding
    • Loading states: Waiting periods that could be entertaining
    • Achievements: Milestones, streaks, completions
    • Interactions: Hover states, clicks, drags
    • Errors: Softening frustrating moments
    • Easter eggs: Hidden discoveries for curious users
  2. Understand the context:

    • What's the brand personality? (Playful? Professional? Quirky? Elegant?)
    • Who's the audience? (Tech-savvy? Creative? Corporate?)
    • What's the emotional context? (Accomplishment? Exploration? Frustration?)
    • What's appropriate? (Banking app ≠ gaming app)
  3. Define delight strategy:

    • Subtle sophistication: Refined micro-interactions (luxury brands)
    • Playful personality: Whimsical illustrations and copy (consumer apps)
    • Helpful surprises: Anticipating needs before users ask (productivity tools)
    • Sensory richness: Satisfying sounds, smooth animations (creative tools)

If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer.

CRITICAL: Delight should enhance usability, never obscure it. If users notice the delight more than accomplishing their goal, you've gone too far.

Delight Principles

Follow these guidelines:

Delight Amplifies, Never Blocks

  • Delight moments should be quick (< 1 second)
  • Never delay core functionality for delight
  • Make delight skippable or subtle
  • Respect user's time and task focus

Surprise and Discovery

  • Hide delightful details for users to discover
  • Reward exploration and curiosity
  • Don't announce every delight moment
  • Let users share discoveries with others

Appropriate to Context

  • Match delight to emotional moment (celebrate success, empathize with errors)
  • Respect the user's state (don't be playful during critical errors)
  • Match brand personality and audience expectations
  • Cultural sensitivity (what's delightful varies by culture)

Compound Over Time

  • Delight should remain fresh with repeated use
  • Vary responses (not same animation every time)
  • Reveal deeper layers with continued use
  • Build anticipation through patterns

Delight Techniques

Add personality and joy through these methods:

Micro-interactions & Animation

Button delight:

/* Satisfying button press */
.button {
  transition: transform 0.1s, box-shadow 0.1s;
}
.button:active {
  transform: translateY(2px);
  box-shadow: 0 2px 4px rgba(0,0,0,0.2);
}

/* Ripple effect on click */
/* Smooth lift on hover */
.button:hover {
  transform: translateY(-2px);
  transition: transform 0.2s cubic-bezier(0.25, 1, 0.5, 1); /* ease-out-quart */
}

Loading delight:

  • Playful loading animations (not just spinners)
  • Personality in loading messages (write product-specific ones, not generic AI filler)
  • Progress indication with encouraging messages
  • Skeleton screens with subtle animations

Success animations:

  • Checkmark draw animation
  • Confetti burst for major achievements
  • Gentle scale + fade for confirmation
  • Satisfying sound effects (subtle)

Hover surprises:

  • Icons that animate on hover
  • Color shifts or glow effects
  • Tooltip reveals with personality
  • Cursor changes (custom cursors for branded experiences)

Personality in Copy

Playful error messages:

"Error 404"
"This page is playing hide and seek. (And winning)"

"Connection failed"
"Looks like the internet took a coffee break. Want to retry?"

Encouraging empty states:

"No projects"
"Your canvas awaits. Create something amazing."

"No messages"
"Inbox zero! You're crushing it today."

Playful labels & tooltips:

"Delete"
"Send to void" (for playful brand)

"Help"
"Rescue me" (tooltip)

IMPORTANT: Match copy personality to brand. Banks shouldn't be wacky, but they can be warm.

Illustrations & Visual Personality

Custom illustrations:

  • Empty state illustrations (not stock icons)
  • Error state illustrations (friendly monsters, quirky characters)
  • Loading state illustrations (animated characters)
  • Success state illustrations (celebrations)

Icon personality:

  • Custom icon set matching brand personality
  • Animated icons (subtle motion on hover/click)
  • Illustrative icons (more detailed than generic)
  • Consistent style across all icons

Background effects:

  • Subtle particle effects
  • Gradient mesh backgrounds
  • Geometric patterns
  • Parallax depth
  • Time-of-day themes (morning vs night)

Satisfying Interactions

Drag and drop delight:

  • Lift effect on drag (shadow, scale)
  • Snap animation when dropped
  • Satisfying placement sound
  • Undo toast ("Dropped in wrong place? [Undo]")

Toggle switches:

  • Smooth slide with spring physics
  • Color transition
  • Haptic feedback on mobile
  • Optional sound effect

Progress & achievements:

  • Streak counters with celebratory milestones
  • Progress bars that "celebrate" at 100%
  • Badge unlocks with animation
  • Playful stats ("You're on fire! 5 days in a row")

Form interactions:

  • Input fields that animate on focus
  • Checkboxes with a satisfying scale pulse when checked
  • Success state that celebrates valid input
  • Auto-grow textareas

Sound Design

Subtle audio cues (when appropriate):

  • Notification sounds (distinctive but not annoying)
  • Success sounds (satisfying "ding")
  • Error sounds (empathetic, not harsh)
  • Typing sounds for chat/messaging
  • Ambient background audio (very subtle)

IMPORTANT:

  • Respect system sound settings
  • Provide mute option
  • Keep volumes quiet (subtle cues, not alarms)
  • Don't play on every interaction (sound fatigue is real)

Easter Eggs & Hidden Delights

Discovery rewards:

  • Konami code unlocks special theme
  • Hidden keyboard shortcuts (Cmd+K for special features)
  • Hover reveals on logos or illustrations
  • Alt text jokes on images (for screen reader users too!)
  • Console messages for developers ("Like what you see? We're hiring!")

Seasonal touches:

  • Holiday themes (subtle, tasteful)
  • Seasonal color shifts
  • Weather-based variations
  • Time-based changes (dark at night, light during day)

Contextual personality:

  • Different messages based on time of day
  • Responses to specific user actions
  • Randomized variations (not same every time)
  • Progressive reveals with continued use

Loading & Waiting States

Make waiting engaging:

  • Interesting loading messages that rotate
  • Progress bars with personality
  • Mini-games during long loads
  • Fun facts or tips while waiting
  • Countdown with encouraging messages
Loading messages — write ones specific to your product, not generic AI filler:
- "Crunching your latest numbers..."
- "Syncing with your team's changes..."
- "Preparing your dashboard..."
- "Checking for updates since yesterday..."

WARNING: Avoid cliched loading messages like "Herding pixels", "Teaching robots to dance", "Consulting the magic 8-ball", "Counting backwards from infinity". These are AI-slop copy — instantly recognizable as machine-generated. Write messages that are specific to what your product actually does.

Celebration Moments

Success celebrations:

  • Confetti for major milestones
  • Animated checkmarks for completions
  • Progress bar celebrations at 100%
  • "Achievement unlocked" style notifications
  • Personalized messages ("You published your 10th article!")

Milestone recognition:

  • First-time actions get special treatment
  • Streak tracking and celebration
  • Progress toward goals
  • Anniversary celebrations

Implementation Patterns

Animation libraries:

  • Framer Motion (React)
  • GSAP (universal)
  • Lottie (After Effects animations)
  • Canvas confetti (party effects)

Sound libraries:

  • Howler.js (audio management)
  • Use-sound (React hook)

Physics libraries:

  • React Spring (spring physics)
  • Popmotion (animation primitives)

IMPORTANT: File size matters. Compress images, optimize animations, lazy load delight features.

NEVER:

  • Delay core functionality for delight
  • Force users through delightful moments (make skippable)
  • Use delight to hide poor UX
  • Overdo it (less is more)
  • Ignore accessibility (animate responsibly, provide alternatives)
  • Make every interaction delightful (special moments should be special)
  • Sacrifice performance for delight
  • Be inappropriate for context (read the room)

Verify Delight Quality

Test that delight actually delights:

  • User reactions: Do users smile? Share screenshots?
  • Doesn't annoy: Still pleasant after 100th time?
  • Doesn't block: Can users opt out or skip?
  • Performant: No jank, no slowdown
  • Appropriate: Matches brand and context
  • Accessible: Works with reduced motion, screen readers

Remember: Delight is the difference between a tool and an experience. Add personality, surprise users positively, and create moments worth sharing. But always respect usability - delight should enhance, never obstruct.

Du fichier au premier essai

Le téléchargement contient exactement le contenu affiché sur cette fiche. Cette copie peut différer de la dernière version du dépôt source.

Consulter la source et ses fichiers annexes

Ce téléchargement contient uniquement SKILL.md. Les scripts, références, modèles et dépendances éventuels ne sont pas inclus. Récupérez les fichiers nécessaires depuis la source en conservant leur arborescence avant de poursuivre.

1. Télécharger le fichier

Télécharger SKILL.md

Depuis la racine d’un projet de test, enregistrez le fichier sous .skill-downloads/add-delightful-moments-to-interfaces-msh3us2m/SKILL.md, ou utilisez la commande suivante. Ce dossier sert à examiner la skill avant son installation.

Commande pour macOS/Linux ou WSL : un shell POSIX et curl sont nécessaires. Sous Windows sans WSL, utilisez le bouton de téléchargement et créez le dossier manuellement.

mkdir -p '.skill-downloads/add-delightful-moments-to-interfaces-msh3us2m' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/add-delightful-moments-to-interfaces-msh3us2m/download' --output '.skill-downloads/add-delightful-moments-to-interfaces-msh3us2m/SKILL.md.part' && mv '.skill-downloads/add-delightful-moments-to-interfaces-msh3us2m/SKILL.md.part' '.skill-downloads/add-delightful-moments-to-interfaces-msh3us2m/SKILL.md'

2. Vérifier les prérequis

Lisez SKILL.md avant de l’utiliser. Si le fichier cite des scripts ou services externes, examinez-les et préparez les accès nécessaires dans votre environnement de test.

Aucune section de prérequis reconnue dans ce fichier. Cela ne signifie pas qu’il est autonome : les bibliothèques, outils et accès peuvent être cités ailleurs dans le contenu ou dans le dépôt source.

Les plateformes de la fiche sont des indications du catalogue. Les chemins ci-dessous suivent la documentation des outils ; ils ne prouvent pas que cette skill y a été exécutée. Aucune version minimale de ces outils n’est attestée pour cette fiche.

3. Charger la skill

Après vérification, copiez le dossier complet dans le projet avec l’une des commandes ci-dessous, puis ouvrez une nouvelle session de l’outil. La commande s’arrête si un dossier du même nom existe déjà : comparez les fichiers avant de le remplacer.

Claude Code
test -f '.skill-downloads/add-delightful-moments-to-interfaces-msh3us2m/SKILL.md' && test -s '.skill-downloads/add-delightful-moments-to-interfaces-msh3us2m/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/delight' && cp -R '.skill-downloads/add-delightful-moments-to-interfaces-msh3us2m' '.claude/skills/delight'

Cursor
test -f '.skill-downloads/add-delightful-moments-to-interfaces-msh3us2m/SKILL.md' && test -s '.skill-downloads/add-delightful-moments-to-interfaces-msh3us2m/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/delight' && cp -R '.skill-downloads/add-delightful-moments-to-interfaces-msh3us2m' '.cursor/skills/delight'

OpenSkills

OpenSkills doit déjà être installé. La procédure locale install/read est contrôlée avec OpenSkills 1.5.0, qui exige Node.js ≥ 20.6.0. Aucun slug du catalogue n’est résolu automatiquement.

Installation officielle d’OpenSkills
openskills install './.skill-downloads/add-delightful-moments-to-interfaces-msh3us2m'

openskills read 'add-delightful-moments-to-interfaces-msh3us2m'

La lecture doit afficher le contenu du fichier installé et son dossier de base. Elle ne lance ni la skill ni ses dépendances.

Pour un agent qui lit AGENTS.md, synchronisez ensuite l’index. Cette commande modifie AGENTS.md : relisez le diff avant de l’utiliser.

openskills sync

Mode manuel ou autre outil : joignez SKILL.md à une conversation, ou ouvrez-le dans un agent capable de lire les fichiers. Ajoutez les ressources annexes nécessaires. Il n’existe pas de dossier universel reconnu par tous les outils.

4. Faire un premier essai

Utilisez une entrée courte et fictive : un endpoint d’API, un petit document ou un brief d’interface. Dans une nouvelle conversation, joignez le fichier ou donnez son chemin à l’agent, puis adaptez cette demande :

Lis .skill-downloads/add-delightful-moments-to-interfaces-msh3us2m/SKILL.md et applique ses instructions à cet exemple : [décrire une entrée de test]. Indique les fichiers, dépendances ou accès qui manquent. Produis le résultat demandé par la skill sans inventer de données ni exécuter de script non examiné.

Résultat attendu : une sortie correspondant aux instructions de la skill, ou une liste précise des prérequis manquants. Une simple confirmation de lecture ne valide pas le premier usage. Si une ressource externe est indisponible, ce parcours reste à tester.

Skills similaires