Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences.
MANDATORY PREPARATION
Context Gathering (Do This First)
You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), brand personality (playful vs professional vs quirky vs elegant), and what's appropriate for the domain.
Attempt to gather these from the current thread or codebase.
If you don't find
exact
information and have to infer from existing design and functionality, you MUST STOP and STOP and call the AskUserQuestionTool to clarify. whether you got it right.
Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST STOP and call the AskUserQuestionTool to clarify. clarifying questions first to complete your context.
Do NOT proceed until you have answers. Delight that's wrong for the context is worse than no delight at all.
Use frontend-design skill
Use the frontend-design skill for design principles and anti-patterns. Do NOT proceed until it has executed and you know all DO's and DON'Ts.
Assess Delight Opportunities
Identify where delight would enhance (not distract from) the experience:
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
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)
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)
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.