Back to Skills

transitions-dev

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 /

1,464stars52forksUpdated 6/22/2026

Security Assessment

Safe(100/100)
Security Score100/100

About transitions-dev

The transitions-dev skill provides eighteen production-ready CSS transition patterns for common web interface animations. It solves the problem of implementing smooth, professional animations without writing transitions from scratch or pulling in heavy framework dependencies. Each transition is namespaced under `t-*` selectors with semantic CSS custom properties, making them portable and conflict-free across projects.

The skill covers essential UI animation patterns including notification badges, dropdown menus, modal dialogs, panel reveals, page transitions, card resizes, number updates, text swaps, icon transitions, success animations, error state shakes, input clearing effects, skeleton loaders, shimmer text, sliding tabs, tooltips, and staggered text reveals. Every transition snippet includes a `prefers-reduced-motion` guard for accessibility. The patterns are framework-agnostic and require only documented HTML hooks to wire up—no demo-specific markup or JavaScript dependencies.

This skill is ideal for frontend developers building web applications who need polished, accessible animations without reinventing common patterns. It's particularly valuable for product teams shipping notification systems, form interfaces, navigation components, loading states, and multi-step workflows. The decision rules help match user requests like "animate the dropdown" or "shake on invalid" to the appropriate transition pattern, making it easy to implement consistent motion design across an application.

FAQ

Do these transitions require a JavaScript framework?

No. All transitions are pure CSS with semantic custom properties. You only need to add the documented HTML hooks and class names to your markup.

Are these transitions accessible?

Yes. Every transition snippet includes a `prefers-reduced-motion` media query guard that respects user motion preferences for accessibility.

Can I customize the timing and easing?

Yes. Each transition uses CSS custom properties for timing, easing, and other parameters, allowing you to override defaults without modifying the core CSS.

What browsers are supported?

The transitions use modern CSS features like custom properties and are designed for current evergreen browsers. Check individual transition docs for specific feature requirements.

How do I choose between similar transitions like modal vs panel reveal?

Follow the decision rules in the documentation. Match based on the visible UI element first (e.g., centered overlay = modal, side region = panel), then the interaction verb (open, reveal, slide).

All Files

20 files
_root.css4.2 KB
View
02-number-pop-in.md3.7 KB
View
05-menu-dropdown.md3.4 KB
View
08-page-side-by-side.md3.3 KB
View
14-skeleton-reveal.md4.6 KB
View
18-texts-reveal.md3.4 KB
View
01-card-resize.md1.6 KB
View
03-notification-badge.md3.9 KB
View
10-success-check.md6.9 KB
View
04-text-states-swap.md3.0 KB
View
07-panel-reveal.md2.7 KB
View
11-avatar-group-hover.md7.2 KB
View
12-error-state-shake.md8.3 KB
View
16-tabs-sliding.md4.5 KB
View
06-modal.md2.7 KB
View
09-icon-swap.md2.3 KB
View
13-input-clear-dissolve.md10.4 KB
View
15-shimmer-text.md3.1 KB
View
17-tooltip.md3.3 KB
View
SKILL.md17.4 KB
View

Install transitions-dev

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill