interaction-delight

Files (4)

• LICENSE.txt
• NOTICE.md
• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# Interaction Delight

Make the experience memorable only where the product has earned it. Delight must reveal product character through a useful interaction, humane response, or considered detail.

This skill owns targeted interaction and emotional polish after the primary flow works. It does not replace foundational design, accessibility, or usability review.

## Find the opportunity

Inspect the target, audience, product voice, usage frequency, emotional stakes, and existing design context. Look for:

- effort worth acknowledging;
- waiting that can become informative;
- empty or first-use states that need orientation;
- errors or recovery moments that need empathy;
- interactions whose physical or verbal response can express the product;
- useful capabilities people might enjoy discovering.

Do not manufacture celebration for ordinary clicks.

## Define one thesis

State what the user should feel and why that feeling belongs to this product. Choose the smallest system that delivers it:

- a response to a meaningful action;
- product-specific language that improves clarity;
- a transition with a coherent material behavior;
- an illustration, sound, haptic, or environmental detail grounded in the product world;
- a discovery reward that reveals real utility.

## Match the moment

- **Success:** scale the response to effort and consequence.
- **Waiting:** show truthful progress or useful context; never fake delay.
- **First use:** make the next action obvious before adding personality.
- **Recovery:** lead with the problem and recovery. Never joke about loss, money, privacy, or blocked work.
- **Repeated use:** keep the response satisfying after the hundredth use.
- **Discovery:** reward curiosity without hiding required functionality.

## Guardrails

Delight must not delay or obscure the primary task, override platform conventions, autoplay sound, ignore reduced motion, add disproportionate dependencies, or become mandatory on repeat.

Verify keyboard, screen-reader, touch, muted, localized, reduced-motion, and low-performance paths. The interface must remain fast and understandable without the flourish.

Implement one coherent delight system, test it in context, and remove any detail that feels transferable to an unrelated product.

From deepaktiwari09/team-agent-skills, MIT.

More from deepaktiwari09/team-agent-skills