Earning a Moment

Delight is a budget, not a style, and the default answer is no. This skill exists to reject nine ideas so the tenth is worth building — a product with one earned moment and uniform polish everywhere else beats a product with six flourishes and a broken focus ring. Boundary with motion: this skill decides whether a moment gets extra craft; motion decides how it moves. Nothing here contains a duration, an easing curve, or a transform — the instant the answer is yes, hand the moment to motion (one element), transitions (a sequence), or gestures (pointer-driven) and stop. If someone is asking which curve their confetti uses, they have already skipped the decision this skill makes.

Read the product's existing personality before proposing anything. Count what is already there: a sound file, a navigator.vibrate call, a confetti dependency (canvas-confetti, react-rewards), a celebration component, a mute preference, a prefers-reduced-motion block. A product with zero flourishes has a deliberate register that one addition changes; a product with four has a consistency problem, and the right proposal is usually to remove three. Whatever survives uses the project's existing motion, sound, and token systems — a delight moment is the worst possible reason to introduce a second animation library.

Quick Reference

The Delight-Impact Curve

Benji Taylor's formulation: "the potential for delight increases as the frequency of feature usage decreases." Rauno Freiberg is credited in Taylor's own /family-values footnotes as a co-source on the frequency-and-novelty axis. Emil Kowalski's frequency gate gives the same curve as four operating rows, and this is the decision procedure — score the moment before discussing it: