
Buttons Ctas
- 356 installs
- 68 repo stars
- Updated December 30, 2025
- dylantarre/animation-principles
buttons-ctas is a Claude Code skill that applies Disney's 12 animation principles to buttons, links, and CTAs—press, hover, loading, and success micro-interactions—for developers polishing frontend conversion UI.
About
buttons-ctas is a frontend animation skill from dylantarre/animation-principles for developers animating buttons, CTAs, and clickable actions. It maps Disney's 12 principles to practical CSS patterns: squash and stretch via scale(0.95) on press, anticipation with translateY(-2px) hover lift, and staging that keeps primary CTAs visually dominant through size, contrast, and motion emphasis. Use it when interfaces feel flat or unresponsive and micro-interactions need consistent tactile feedback across loading and success states. The skill triggers when animating buttons or action elements in Claude Code or Cursor. Reach for buttons-ctas when improving conversion clarity on web or app CTAs without building a full motion design system from scratch.
- Hover, press, and release micro-feedback
- Loading and success states on primary CTAs
- Magnetic or emphasis effects used judiciously
- Conversion-safe motion on checkout actions
- Accessible reduced-motion alternatives
Buttons Ctas by the numbers
- 356 all-time installs (skills.sh)
- Ranked #694 of 2,245 Frontend Development skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/dylantarre/animation-principles --skill buttons-ctasAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 356 |
|---|---|
| repo stars | ★ 68 |
| Last updated | December 30, 2025 |
| Repository | dylantarre/animation-principles ↗ |
How do you animate button press and hover states?
Polish primary and secondary buttons, links, and CTAs with press, hover, loading, and success micro-interactions that increase clarity and conversion.
Who is it for?
Frontend developers polishing button and CTA micro-interactions who want principle-driven CSS motion patterns.
Skip if: Developers building complex page transitions or navigation shells—use navigation-menus instead—or teams avoiding CSS animation entirely.
When should I use this skill?
User animates buttons, CTAs, clickable actions, press/hover/loading/success states, or conversion-focused micro-interactions
What you get
CSS button micro-interactions with press scale, hover lift, loading states, and primary CTA motion hierarchy
- animated button CSS
- CTA micro-interaction patterns
- loading and success state styles
By the numbers
- Applies Disney's 12 animation principles to buttons and CTAs
- Uses transform: scale(0.95) on press and translateY(-2px) on hover
Files
Button & CTA Animation Principles
Apply Disney's 12 principles to create buttons that feel alive and responsive.
Principles Applied to Buttons
1. Squash & Stretch
Scale buttons slightly on press: transform: scale(0.95) on :active, return to scale(1) on release. Creates tactile feedback.
2. Anticipation
Subtle hover lift before click: transform: translateY(-2px) prepares users for the action.
3. Staging
Primary CTAs should be visually prominent. Use size, color contrast, and whitespace. Animate primary buttons more boldly than secondary.
4. Straight Ahead & Pose to Pose
Use pose-to-pose for button states: define clear keyframes for default, hover, active, and disabled states.
5. Follow Through & Overlapping Action
After click, let shadows or glows settle slightly after the button returns. Icon inside can lag 20-50ms behind button movement.
6. Ease In & Ease Out
Never use linear timing. Use ease-out for hover-in (fast start), ease-in for hover-out (gentle exit). cubic-bezier(0.4, 0, 0.2, 1) works well.
7. Arcs
Floating action buttons should move in arcs when repositioning. Use transform with easing rather than straight-line movement.
8. Secondary Action
Ripple effects, icon rotations, or shadow changes accompany the primary scale/color change. Don't let secondary actions overpower.
9. Timing
- Hover: 150-200ms
- Active/press: 50-100ms (snappy)
- Focus ring: 150ms
- Loading state transition: 200-300ms
10. Exaggeration
Success buttons can briefly scale to 1.05 before settling. Error states can include subtle shake (3-5px, 2-3 cycles).
11. Solid Drawing
Maintain consistent border-radius and proportions across states. Shadows should respect light source direction throughout.
12. Appeal
Round corners feel friendly, sharp corners feel professional. Match button personality to brand. Satisfying click feedback increases conversions.
CSS Implementation
.btn {
transition: transform 150ms ease-out,
box-shadow 150ms ease-out,
background-color 150ms ease-out;
}
.btn:hover {
transform: translateY(-2px);
box-shadow: 0 4px 12px rgba(0,0,0,0.15);
}
.btn:active {
transform: scale(0.97) translateY(0);
transition-duration: 50ms;
}Key Properties
transform: scale, translatebox-shadow: depth changesbackground-color: state indicationopacity: disabled statesfilter: brightness on hover
Related skills
FAQ
Which animation principles does buttons-ctas apply?
buttons-ctas applies Disney's 12 principles to buttons and CTAs, including squash and stretch on press with scale(0.95), anticipation via translateY(-2px) hover lift, and staging that emphasizes primary actions through size and contrast.
What CSS patterns does buttons-ctas recommend?
buttons-ctas recommends transform-based press scaling, hover lift, and differentiated motion for primary versus secondary CTAs. The skill also covers loading and success states for clearer action feedback.