Agent Hub

transitions-dev

Properties1
tagsskill, marketing

11 min read

Skill

Owner: Stark · Team: Stark · Source: ~/.openclaw/workspace-social/skills/transitions-dev/SKILL.md

Production-ready CSS transitions for web apps. Use when implementing notification badges, dropdowns, modals, panel reveals, page transitions, card resizes, number pop-ins, text swaps, icon swaps, success checks, avatar group hovers, error state shakes, search/input clear, skeleton loaders, shimmer text, sliding tabs, tooltips, or staggered text reveals. Triggers on “add a transition”, “animate the dropdown”, “make the modal open smoothly”, “swap icon”, “page slide”, “stagger animation”, “open / close transition”, “make it animate”, “fade between”, “success animation”, “form error”, “shake on invalid”, “hover lift”, “avatar stack hover”, “clear the search”, “skeleton loader”, “loading shimmer”, “shimmer text”, “sliding tabs”, “segmented control”, “tooltip”, “reveal text”. Also transitions reveal, transitions review, transitions apply, transitions refine.

Playbook (mirrored from disk)

Transitions.dev

Eighteen portable CSS transitions, each namespaced under t-* selectors with semantic CSS custom properties. Drop-in: paste the snippet, wire the documented HTML hooks, done. No framework dependencies, no demo-specific markup, and every snippet ships a prefers-reduced-motion guard.

Quick reference

TransitionWhen to useReference
Card resizeTween a container’s width or height when its layout state changes.01-card-resize.md
Number pop-inRe-enter each digit with a blurred slide when a number updates.02-number-pop-in.md
Notification badgeSlide a small badge onto a trigger and pop the dot.03-notification-badge.md
Text states swapSwap text in place with a blurred up-and-down transition.04-text-states-swap.md
Menu dropdownOpen an origin-aware dropdown that grows from its trigger.05-menu-dropdown.md
Modal open / closeScale-up modal dialog with a softer scale-down on close.06-modal.md
Panel revealSlide a panel into a region with a cross-blur.07-panel-reveal.md
Page side-by-sideSlide between two side-by-side pages (list ↔ detail, step 1 ↔ step 2).08-page-side-by-side.md
Icon swapCross-fade two icons in the same slot with blur and scale.09-icon-swap.md
Success checkCompose fade + rotate + Y-bob + path stroke-draw to celebrate a completed action.10-success-check.md
Avatar group hoverDistance-falloff lift on a row of items with a bouncy spring on return.11-avatar-group-hover.md
Error state shakePer-segment cubic-bezier shake with auto-reverting border + message.12-error-state-shake.md
Input clear with dissolveFly-out + per-word streak when a text field is cleared.13-input-clear-dissolve.md
Skeleton loader and revealPulse a placeholder, then cross-fade + cross-blur to the loaded content.14-skeleton-reveal.md
Shimmer textSweep a highlight band across muted text on a loop (pure CSS).15-shimmer-text.md
Tabs slidingSlide the active pill between tabs in a segmented control.16-tabs-sliding.md
Tooltip open/closeDelayed fade+scale in, instant out (pure CSS).17-tooltip.md
Texts revealStaggered blurred rise for stacked text lines, quiet fade out.18-texts-reveal.md

Decision rules

When the user asks for a transition, match against the visible UI element first, then the verb:

  • Trigger + small dot floating on top → notification badge.
  • Trigger + surface that grows from it → dropdown (anchored, origin-aware) or modal (centered, no anchor).
  • Surface that slides into a region of the page → panel reveal.
  • Two screens, list ↔ detail or step 1 ↔ step 2 → page side-by-side.
  • Element changes width or height → card resize.
  • Element’s text content changes in place → text states swap.
  • Two icons in the same slot → icon swap.
  • A number updates → number pop-in.
  • Confirmation / success / “done” moment (checkmark, payment processed, file uploaded) → success check.
  • Hovering an item in a horizontal stack (avatars, chips, segmented buttons, tag pills) → avatar group hover.
  • Form validation error / “this is wrong” feedback (invalid field, wrong PIN, duplicate name) → error state shake.
  • Clearing a text field (search box × button, filter reset) → input clear with dissolve.
  • Placeholder that loads then swaps to real content (list row, card, profile header) → skeleton loader and reveal.
  • In-progress / “thinking” text that should feel alive (loading label, streaming status) → shimmer text.
  • Small horizontal set of mutually-exclusive options with a moving highlight (view switcher, segmented control, filter tabs) → tabs sliding.
  • Hover/focus hint that appears over a trigger (icon tooltip, info bubble) → tooltip open / close.
  • Stacked headline + supporting line entering with rhythm (hero copy, empty state, onboarding step) → texts reveal.
  • No clear match → fall back to transitions reveal and let the user pick. Don’t guess.

If two transitions could fit, prefer the lower-overhead one (card resize over panel reveal, dropdown over modal, success check over a full modal celebration) unless the design clearly calls for the heavier surface. The success check is animation-only — if you also need to swap from a spinner to the check, pair it with icon swap.

Commands

The skill exposes four namespaced verbs the agent should recognise in addition to direct transition requests. Every command starts with transitions so the invocation never collides with verbs from other skills installed in the same project.

transitions reveal — list every transition

Trigger phrases: transitions reveal, “reveal the transitions”, “list all transitions”, “what transitions are in this skill”, “show the transitions catalog”.

Behaviour: print the eighteen transitions as a numbered plain-text list — name, one-line summary, and the matching reference filename. Reuse the rows in ## Quick reference above; do not invent new copy. No project access.

transitions review — audit the project for fit

Trigger phrases: transitions review, “review my project”, “audit my animations”, “where would transitions.dev help”, “find places to use this skill”.

Behaviour:

  1. Search the workspace for indicators: transition: declarations, @keyframes, hardcoded ms / s durations in style files, components matching the decision-rule patterns (modals, dropdowns, badges, search inputs, skeletons, tabs, tooltips, …).
  2. For each hit, match against the decision rules and pick the single best-fit transition.
  3. Output a numbered list grouped by file:
    • path/to/Component.tsx:L42 — looks like a dropdown opening, suggest menu-dropdown (05-menu-dropdown.md).
    • Skip ad-hoc transitions that already use a t-* class.
  4. Do not edit anything. End with: “Run transitions apply on any line to install the suggested transition.”

transitions apply — install the best-fit transition

Trigger phrases: transitions apply, “apply a transition here”, “add the right transition”, “install transitions-dev here”, “fix the animation on this element”.

Behaviour:

  1. Read context: the currently-open file, the element nearest the cursor, surrounding CSS / JSX. If the user named a transition explicitly (e.g. transitions apply menu-dropdown), use it.
  2. Run the decision rules from ## Decision rules on that context and pick one transition. If two could fit, prefer the lower-overhead one (same tie-breaker the existing rules use).
  3. Surface a one-line proposal: “I’d apply menu-dropdown here because the element opens from a trigger and is anchored. Confirm to install?”.
  4. On confirmation, follow the existing five-step procedure in ## Output format verbatim (root block, snippet, hooks, reduced-motion guard, JS orchestration if needed).
  5. If the agent can’t pick a single transition with confidence, fall back to transitions reveal and ask the user to choose.

transitions refine — align existing values to the motion tokens

Trigger phrases: transitions refine, “refine my transitions”, “improve the animation values”, “tune the durations / easing”, “make the timing consistent”, “align to the motion tokens”.

Behaviour:

  1. Search style files for transition/animation values: transition / animation shorthands, @keyframes, durations (…ms / …s), easing (cubic-bezier(...) or keywords), translate distances (px), scale(...), and blur(...).
  2. For each declaration, infer what it does (modal close, dropdown open, tooltip, badge appear, text reveal, page slide, shake, …) from the surrounding selectors plus the ## Decision rules.
  3. Look the usage up in ## Motion tokens and read the recommended duration, easing, distance, scale, and blur for it.
  4. Output a numbered list grouped by file of only the values that differ from the token: path/to/Component.css:L42 — modal close 300ms → 150ms (Quick), ease → cubic-bezier(0.22, 1, 0.36, 1) (Smooth ease out). Note any value with no matching usage and leave it untouched.
  5. Do not edit anything. End with: “Confirm any line to apply the change, or run transitions apply to install a full transition instead.”

Motion tokens

The value vocabulary behind the eighteen transitions. transitions refine maps each existing value to a usage below, then suggests the token whose value differs. Match on usage, not on the raw number — a 300ms modal close is still a Quick (150ms) close.

Durations

ValueNameUsage
40msStaggerper-item stagger offset
80msMicrotooltip delay, shake segment, large stagger
150msQuickmodal close, dropdown close, text swap, tooltip appear
250msFasticon swap, dropdown open, modal open, tabs sliding, page slide
350msMediumpanel close, toast close
400msSlowpanel open, skeleton content reveal, input clear
500msVery slowemphasis moments, badge appear, text reveal, success check

Easings

ValueNameUsage
cubic-bezier(0.22, 1, 0.36, 1)Smooth ease outmodal / dropdown / panel open + close, page slide, resize, position change
ease-in-outEase in outicon swap, text swap, text reveal, skeleton reveal
ease-outEase outtooltip open / close
linearLinearshimmer, skeleton pulse, spinner
cubic-bezier(0.34, 1.36, 0.64, 1)Bouncy overshootbadge pop open
cubic-bezier(0.34, 3.85, 0.64, 1)Strong bouncy overshootbouncy hover-out (avatar return)

Distances

ValueNameUsage
4pxMicrotext swap
6pxSmallerror shake (small segment)
8pxBasebadge diagonal reveal, page slide, error shake (large segment)
12pxMediumtext reveal
30pxLargecheck badge appear

Scales

ValueNameUsage
0.96Largemodal open / close
0.97Mediumdropdown open
0.98Smalltooltip open
0.99Tinydropdown close

Blur

ValueNameUsage
2pxSmallpanel reveal, icon swap, text swap, skeleton reveal, number pop-in
3pxMediumpage slide, text reveal
8pxLargesuccess check open

Universal install

Copy _root.css into your project once and import it (or paste its :root block into your global stylesheet). It defines the semantic tunable variables for all eighteen transitions. Every snippet reads from these names — --resize-*, --badge-*, --dropdown-*, --clear-*, --shimmer-*, --tabs-*, --tt-*, --stagger-*, and the rest.

Each reference file also restates just the variables that snippet needs, so you can install a single transition without pulling the whole block. Don’t duplicate the block — if _root.css is already imported, skip re-pasting any per-snippet :root.

The --pX-* source tokens used by the live demo at transitions.dev are intentionally not exported. Tunable values are renamed to semantic names so the user owns the design vocabulary. A few transitions (input clear, shimmer text, tabs, tooltip) carry color tokens that differ by theme — each reference file documents the html[data-theme="dark"] overrides.

Output format

When inserting a transition into the user’s project:

  1. Install the variables from _root.css into the user’s global stylesheet, but only if they aren’t already there — or just the per-snippet :root block from the reference file if installing a single transition. If the universal block is already imported, do not duplicate it.
  2. Paste the chosen transition’s CSS verbatim from the relevant reference file. Do not rewrite selectors, do not collapse the transition into shorthand, do not strip will-change. The snippets are tuned and tested.
  3. Wire the documented HTML hooks — class names (.t-dropdown, .t-modal, .t-success-check, .t-avatar, .t-clear, .t-skel, .t-shimmer, .t-tabs, .t-tt, .t-stagger, …) and state attributes (data-open, data-state, data-page, aria-selected, .is-open, .is-closing, .is-error, .is-shaking, .has-value, .is-clearing, .is-pulsing, .is-revealed, .is-shown, .is-hiding).
  4. Preserve the @media (prefers-reduced-motion: reduce) block. Every snippet ships one. Removing it makes the component fail accessibility audits.
  5. For transitions that need JS (dropdown, modal, text swap, number pop-in, page slide, success check, avatar group hover, error state shake, input clear, skeleton reveal, tabs sliding, texts reveal), copy the small orchestration snippet from the reference file and adapt the selectors to the user’s DOM. Keep the timing reads (getComputedStyle(...)getPropertyValue("--…")) so durations stay in sync with the :root values. Shimmer text and tooltip are pure CSS — no JS needed.

Keep the diff small: only edit the files needed to introduce the transition. Don’t rename the user’s existing variables, don’t reformat unrelated CSS, don’t pull in a motion library.

Common mistakes to avoid

  • Stripping the close-state class cleanup on dropdown/modal — without the setTimeout that removes .is-closing, the next open jumps from the closing scale instead of the resting pre-open scale.
  • Forgetting the reflow in the text swap, number pop-in, success check replay, and error state shake — void el.offsetWidth (or offsetHeight) between class/attribute removal and re-addition is what guarantees the animation replays.
  • Animating a single container instead of the inner pieces — for the badge, animate the dot, not the trigger; for page slide, animate the page sections, not the container.
  • Replacing transition: … with transition: all — every snippet enumerates exact properties on purpose so unrelated style changes don’t ride in for free.
  • Hardcoding the success check’s stroke-dasharray — the snippet ships 20 as a placeholder. Replace it with path.getTotalLength() rounded up by 1 for your path, otherwise the stroke pre-reveals or over-draws.
  • Setting transition-timing-function in CSS for the avatar group hover — it has to be set inline in JS before the --shift / --scale-active writes so the bouncy ease-out only applies on mouseleave.
  • Mixing .is-error and .is-shaking into one class for the error state shake — keeping them orthogonal is what allows the shake to replay (remove → reflow → re-add) without flickering the whole error treatment.
  • Leaving the input clear glow on mix-blend-mode: multiply in dark mode — flip to screen, bump --glow-opacity to ~0.85, and paint white gradients in JS.
  • Forgetting to write the tabs pill’s first position without a transition — on first paint and resize, set transform + width with transition: none (then reflow + restore) or the pill animates in from translateX(0) / width: 0.

Reference files

Graph View