Skip to content
Agent Orchestration
Skill

/delight

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.

BOOST
From plugin
ccg
5.9k47 skills19 commands
Install
$ npx -y skills add fengshao1227/ccg-workflow --skill delight --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/delight

Context preview

The summary Claude sees to decide when to auto-load this skill.

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.

SKILL.md

delight.SKILL.md
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."
argument-hint: "[target]"
user-invocable: false

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 using AskUserQuestion.

**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%
  • Bad
Read more
Ships withccg

多模型协作工作流引擎 — /ccg:go 一个命令,AI 自动分析意图、选择策略、编排 Codex + Gemini + Claude 协作执行

Get the whole plugin

Other skills on ccg.

verify-change
Skill

verify-change

变更校验关卡。分析代码变更,检测文档同步状态,评估变更影响范围。当用户提到变更检查、文档同步、代码审查、提交前检查、diff分析时使用。在设计级变更、重构完成时自动触发。

verify-module
Skill

verify-module

模块完整性校验关卡。扫描目录结构、检测缺失文档、验证代码与文档同步。当用户提到模块校验、文档检查、结构完整性、README检查、DESIGN检查时使用。在新建模块完成时自动触发。

verify-quality
Skill

verify-quality

代码质量校验关卡。检测复杂度、重复代码、命名规范、函数长度等质量指标。当用户提到代码质量、复杂度检查、代码异味、重构建议、lint检查、代码规范时使用。在复杂模块、重构完成时自动触发。

verify-security
Skill

verify-security

安全校验关卡。自动扫描代码安全漏洞,检测危险模式,确保安全决策有文档记录。当用户提到安全扫描、漏洞检测、安全审计、代码安全、OWASP、注入检测、敏感信息泄露时使用。在新建模块、安全相关变…