Documentation

Interfaces ship silent. Every button, dialog, and toggle in your app already communicates through motion and color, but never through sound. The web's best component libraries have zero audio story, and the tools that do exist treat sound as decoration: generic effect players with no meaning, no system, and no respect for the user.

sensory-ui is the opposite bet: sound as semantics. Every cue maps to an interaction type across 17 roles and 5 categories. Every pack plays the same language in a different voice. Everything is opt-in, accessibility-first, and synthesized live with the Web Audio API. Zero audio files.

17 sound roles

One language for taps, toggles, navigation, notifications, and celebrations.

9 sound packs

Aero, glass, arcade, and more: same roles, different character.

24 components

Every shadcn/ui primitive with a sound prop and a live demo.

5 guides

Little books on taste, choreography, and craft.

Why this exists

I kept noticing the gap: visual design systems obsess over spacing scales, motion curves, and color tokens, then leave the entire auditory channel untouched. Products either stay mute or bolt on random click sounds that annoy faster than they inform. There was no shadcn-native way to add meaningful audio feedback: typed roles, swappable packs, per-category kill-switches, and prefers-reduced-motion baked in from the start. So I built it.

Satyam Vyas, creator of sensory-ui. If it makes your product feel alive, consider sponsoring.