delight

Identify delight opportunities in onboarding, empty, success, loading, and error states.

Updated Mar 11, 2026

Search Tags:#onboarding #accessibility #usability #delight #micro-interactions #empty-states #brand-personality

Ready to run

npx skills add https://github.com/jkhowland/jkhowland --skill delight-jkhowland

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: delight
Source: https://github.com/jkhowland/jkhowland/tree/main/.claude/skills/delight
Command: npx skills add https://github.com/jkhowland/jkhowland --skill delight-jkhowland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful.

Core Features & Use Cases

Identify natural delight moments in success states, empty states, loading states, achievements, interactions, errors, and Easter eggs.
Align delight strategy with brand personality and audience, balancing playfulness, professionalism, or elegance.
Provide guidelines for implementing micro-interactions, copy, illustrations, sounds, and visuals that are non-blocking and accessible.

Quick Start

Identify opportunities to add delightful moments in the current interface and document the recommended interactions.

Frequently Asked Questions about delight

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What are micro-interactions and how do they add delight to UI empty states?▼

Micro-interactions are small, non-blocking visual or functional touches that add joy to UI empty states. They transform blank screens into engaging moments by aligning visuals and copy with brand personality without hindering usability.

How do I identify natural delight moments for onboarding and loading states?▼

Identify delight moments by mapping user touchpoints across onboarding, loading, and success states. Look for opportunities to inject brand personality through micro-interactions, ensuring the enhancements remain non-blocking and accessible to all users.

Can I add brand personality to error states without hurting accessibility?▼

Yes, you can add brand personality to error states by implementing accessible delight patterns. Ensure micro-interactions, custom copy, and visuals remain non-blocking, respect brand context, and do not interfere with screen readers or keyboard navigation.

What is the best way to align delight strategy with brand personality across web and mobile?▼

Align delight strategy by evaluating your brand context and audience to balance playfulness with professionalism. Apply consistent micro-interactions, illustrations, and non-blocking visuals across both web and mobile products for a cohesive user experience.

Do I need YAML frontmatter to implement accessible delight patterns?▼

Yes, YAML frontmatter with name and description fields is required to implement these accessible delight patterns. The setup supports optional scripts, references, and assets to properly document and execute non-blocking interactions.

When should I avoid adding micro-interactions to user interface touchpoints?▼

Avoid adding micro-interactions when they block user workflows or compromise accessibility. If a delight pattern distracts from core functionality, clashes with a strict professional brand context, or prevents task completion, it should be omitted.