Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
raphaelsalaja avatar

To Spring Or Not To Spring

  • 155 installs
  • 32 repo stars
  • Updated March 17, 2026
  • raphaelsalaja/skill

Audit motion code so gestures use springs, system feedback uses easing, and high-frequency UI skips animation noise—with file:line findings.

About

To Spring or Not To Spring is a checker skill for solo builders shipping polished web and mobile UI who want motion that feels intentional, not accidentally springy or sluggish. It reads animation-related code you point at, then applies a prioritized rule set across spring selection, easing selection, duration, and cases where animation should be disabled entirely. The core question is whether motion reacts to the user or communicates system state—gestures and drags should survive interruption with springs, while toasts and route changes need predictable easing endpoints. Outputs are concrete file:line findings so Claude Code, Cursor, or Codex can patch violations in place. Use it while implementing interactions, when animations feel wrong, or during Ship review before release. Intermediate familiarity with CSS transitions, WAAPI, or motion libraries helps, but the skill encodes the decision logic so you do not memorize timing theory.

  • 4 rule categories: Spring Selection, Easing Selection, Duration, No Animation (prefixes spring-, easing-, duration-, non
  • Decision framework: user-driven motion → spring; system-driven → easing; progress → linear; high-frequency → none
  • Reviews specified files and reports violations in file:line format for agent or human fixes
  • Covers gesture-driven interactions, state transitions, loading/progress, and fast toggles

To Spring Or Not To Spring by the numbers

  • 155 all-time installs (skills.sh)
  • +8 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #1,001 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/raphaelsalaja/skill --skill to-spring-or-not-to-spring

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs155
repo stars32
Security audit3 / 3 scanners passed
Last updatedMarch 17, 2026
Repositoryraphaelsalaja/skill

What it does

Audit motion code so gestures use springs, system feedback uses easing, and high-frequency UI skips animation noise—with file:line findings.

Files

SKILL.mdMarkdownGitHub ↗

To Spring or Not To Spring

Review animation code for correct timing function selection based on interaction type.

How It Works

1. Read the specified files (or prompt user for files/pattern) 2. Check against all rules below 3. Output findings in file:line format

Rule Categories

PriorityCategoryPrefix
1Spring Selectionspring-
2Easing Selectioneasing-
3Durationduration-
4No Animationnone-

Decision Framework

Ask: Is this motion reacting to the user, or is the system speaking?

Motion TypeBest ChoiceWhy
User-driven (drag, flick, gesture)SpringSurvives interruption, preserves velocity
System-driven (state change, feedback)EasingClear start/end, predictable timing
Time representation (progress, loading)Linear1:1 relationship between time and progress
High-frequency (typing, fast toggles)NoneAnimation adds noise, feels slower

Rules

Spring Selection Rules

spring-for-gestures

Gesture-driven motion (drag, flick, swipe) must use springs.

Fail:

<motion.div
  drag="x"
  transition={{ duration: 0.3, ease: "easeOut" }}
/>

Pass:

<motion.div
  drag="x"
  transition={{ type: "spring", stiffness: 500, damping: 30 }}
/>
spring-for-interruptible

Motion that can be interrupted must use springs.

Fail:

// User can click again mid-animation
<motion.div
  animate={{ x: isOpen ? 200 : 0 }}
  transition={{ duration: 0.3 }}
/>

Pass:

<motion.div
  animate={{ x: isOpen ? 200 : 0 }}
  transition={{ type: "spring", stiffness: 400, damping: 25 }}
/>
spring-preserves-velocity

When velocity matters, use springs to preserve input energy.

Fail:

// Fast flick and slow flick animate identically
onDragEnd={(e, info) => {
  animate(target, { x: 0 }, { duration: 0.3 });
}}

Pass:

// Fast flick moves faster than slow flick
onDragEnd={(e, info) => {
  animate(target, { x: 0 }, {
    type: "spring",
    velocity: info.velocity.x,
  });
}}
spring-params-balanced

Spring parameters must be balanced; avoid excessive oscillation.

Fail:

transition={{
  type: "spring",
  stiffness: 1000,
  damping: 5, // Too low - excessive bounce
}}

Pass:

transition={{
  type: "spring",
  stiffness: 500,
  damping: 30, // Balanced - settles quickly
}}

Easing Selection Rules

easing-for-state-change

System-initiated state changes should use easing curves.

Fail:

// Toast notification using spring
<motion.div
  animate={{ y: 0 }}
  transition={{ type: "spring" }}
/>
// Feels restless for a simple announcement

Pass:

<motion.div
  animate={{ y: 0 }}
  transition={{ duration: 0.2, ease: "easeOut" }}
/>
easing-entrance-ease-out

Entrances must use ease-out (arrive fast, settle gently).

Fail:

.modal-enter {
  animation-timing-function: ease-in;
}

Pass:

.modal-enter {
  animation-timing-function: ease-out;
}
easing-exit-ease-in

Exits must use ease-in (build momentum before departure).

Fail:

.modal-exit {
  animation-timing-function: ease-out;
}

Pass:

.modal-exit {
  animation-timing-function: ease-in;
}
easing-transition-ease-in-out

View/mode transitions use ease-in-out for neutral attention.

Pass:

.page-transition {
  animation-timing-function: ease-in-out;
}
easing-linear-only-progress

Linear easing only for progress bars and time representation.

Fail:

.card-slide {
  transition: transform 200ms linear; /* Mechanical feel */
}

Pass:

.progress-bar {
  transition: width 100ms linear; /* Honest time representation */
}

Duration Rules

duration-press-hover

Press and hover interactions: 120-180ms.

Fail:

.button:hover {
  transition: background-color 400ms;
}

Pass:

.button:hover {
  transition: background-color 150ms;
}
duration-small-state

Small state changes: 180-260ms.

Pass:

.toggle {
  transition: transform 200ms ease;
}
duration-max-300ms

User-initiated animations must not exceed 300ms.

Fail:

<motion.div transition={{ duration: 0.5 }} />

Pass:

<motion.div transition={{ duration: 0.25 }} />
duration-shorten-before-curve

If animation feels slow, shorten duration before adjusting curve.

Fail (common mistake):

/* Trying to fix slowness with sharper curve */
.element {
  transition: 400ms cubic-bezier(0, 0.9, 0.1, 1);
}

Pass:

/* Fix slowness with shorter duration */
.element {
  transition: 200ms ease-out;
}

No Animation Rules

none-high-frequency

High-frequency interactions should have no animation.

Fail:

// Animated on every keystroke
function SearchInput() {
  return (
    <motion.div animate={{ scale: [1, 1.02, 1] }}>
      <input onChange={handleSearch} />
    </motion.div>
  );
}

Pass:

function SearchInput() {
  return <input onChange={handleSearch} />;
}
none-keyboard-navigation

Keyboard navigation should be instant, no animation.

Fail:

function Menu() {
  return items.map(item => (
    <motion.li
      whileFocus={{ scale: 1.05 }}
      transition={{ duration: 0.2 }}
    />
  ));
}

Pass:

function Menu() {
  return items.map(item => (
    <li className={styles.menuItem} /> // CSS :focus-visible only
  ));
}
none-context-menu-entrance

Context menus should not animate on entrance (exit only).

Fail:

<motion.div
  initial={{ opacity: 0, scale: 0.95 }}
  animate={{ opacity: 1, scale: 1 }}
  exit={{ opacity: 0 }}
/>

Pass:

<motion.div exit={{ opacity: 0, scale: 0.95 }} />

Output Format

When reviewing files, output findings as:

file:line - [rule-id] description of issue

Example:
components/drawer/index.tsx:45 - [spring-for-gestures] Drag interaction using easing instead of spring
components/modal/styles.module.css:23 - [easing-entrance-ease-out] Modal entrance using ease-in

Summary Table

After findings, output a summary:

RuleCountSeverity
spring-for-gestures2HIGH
easing-entrance-ease-out1MEDIUM
duration-max-300ms3MEDIUM

Quick Reference

InteractionTimingType
Drag releaseSpringstiffness: 500, damping: 30
Button press150msease
Modal enter200msease-out
Modal exit150msease-in
Page transition250msease-in-out
Progress barvarieslinear
Typing feedback0msnone

References

Related skills

FAQ

Is To Spring Or Not To Spring safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.