AI SummaryDelight is a skill booster that helps developers add joyful, personality-driven touches to interfaces—transforming functional designs into memorable user experiences. It benefits product teams, UX-focused developers, and anyone building customer-facing applications.
Install
# Install all 18 skills from impeccable mkdir -p .cursor/skills/adapt && curl --retry 3 --retry-delay 2 --retry-all-errors -fsSL -o .cursor/skills/adapt/SKILL.md "https://raw.githubusercontent.com/pbakaus/impeccable/main/.claude/skills/adapt/SKILL.md" && \
Run in your IDE terminal (bash). On Windows, use Git Bash, WSL, or your IDE's built-in terminal. If curl fails with an SSL error, your network may block raw.githubusercontent.com — try using a VPN or download the files directly from the source repo.
Description
Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful.
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) • Sensory richness: Satisfying sounds, smooth animations (creative tools) If any of these are unclear from the codebase, STOP and call the AskUserQuestionTool to clarify. 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:
Quality Score
Acceptable
68/100
Trust & Transparency
Open Source — Apache-2.0
Source code publicly auditable
Verified Open Source
Hosted on GitHub — publicly auditable
Actively Maintained
Last commit Today
8.4k stars — Strong Community
328 forks
My Fox Den
Community Rating
Sign in to rate this booster