Skip to content

Now in the official shadcn registry directory.

Start free

Particle buttons

Five takes on emitted particles: a hover burst, a click confetti, a continuous sparkle, rising sparks and a click pop. Each is sized and token-driven, with fixed deterministic angles.

ButtonsParticle

Installation

The styled layer is free and installs like any other ai2 component.

Run the following command

npx shadcn@latest add @ai2/buttons-particle

Dependencies, the @ai2/tokens theme and the component file are installed together.

Variations

5 takes on the same idea. Each is its own export, and every one accepts a size prop (sm, md, lg, xl) aligned to the base Button scale.

Burst

Token dots scatter outward on hover.

sm
md
lg
xl

Confetti

Multi-token pieces spray upward on click.

sm
md
lg
xl

Sparkle

Token star dots twinkle continuously around the label.

sm
md
lg
xl

Rise

Warm token sparks rise continuously from the base.

sm
md
lg
xl

Pop

A few larger token particles fire out on click.

sm
md
lg
xl

ai2 Particle buttons: 5 styled variations on the token system

The ai2 Particle buttons are a set of 5 decorative button variations from the styled layer of the @ai2 design system, built around emitted token particles. They are free and MIT licensed, and every color comes from a semantic token, so they theme with the rest of ai2 in light and dark.

Motion runs on framer-motion: framer-motion fires the particles along fixed deterministic angles on hover, click, or in a loop. The styled layer is opt-in, so the dependency only lands if you use it; the base components stay lean. Under reduced motion, no particles are emitted and the buttons behave plainly.

What is in the ai2 Particle buttons?

5 exports in one file: Burst, Confetti, Sparkle, Rise and Pop. Each renders a native button and takes a size prop (sm, md, lg, xl) aligned to the base Button. They are separate from the base Button on purpose: the base keeps its clean variant, tone and size axes, while the styled layer carries the effects.

You own the file. Copy the one category file and you have all 5 variations, with no runtime dependency on ai2 itself.

Why use it

  • On-system by construction: Every color resolves to an ai2 semantic token, so the buttons follow your theme in light and dark with no extra work.
  • Effect without the sprawl: The decorations live in a dedicated styled file, so the base Button keeps its clean, predictable API.
  • Accessible and honest: Each renders a real button element, keeps a visible focus ring, and respects prefers-reduced-motion.

Features

  • Token-driven color: No hardcoded hex or oklch; the look recolors with your theme tokens.
  • framer-motion: framer-motion fires the particles along fixed deterministic angles on hover, click, or in a loop.
  • Reduced-motion aware: Under prefers-reduced-motion, no particles are emitted and the buttons behave plainly.
  • Size aligned to the base: Every variation takes sm, md, lg and xl matching the base Button height scale, so styled and base buttons line up in a row.

Production tips

  • Use it for emphasis, not everywhere: Styled buttons draw the eye. Reserve them for the one action you want people to take on a screen, and use the base Button for the rest.
  • Keep labels as verbs: The decoration adds weight, so a clear action label keeps the button scannable.
  • Pick one variation per surface: The variations share a family; using two different ones in the same view competes for attention.

Works with the rest of ai2

The Particle buttons sit alongside the base Button and the rest of the @ai2 registry. They share the same token file, so a styled action next to a base button or a badge stays visually consistent in both modes.

FAQs

Get new components in your inbox

Component drops, new themes and release notes. No spam, and you can unsubscribe from any email.

© 2026 ai2 design system · MIT licensed · Built with its own components