sound-engine
Skill0 starsChanged 4 months agoMITView on GitHub
Web Audio API sound design system for UI interactions. Synthesizes tactile, iPhone-y sounds (clicks, ticks, whooshes, chimes) with zero external files. React context provider + floating toggle button. Sound off by default.
In this repository37 other files it gives its agents.
- .agents/skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- vercel-composition-patterns/AGENTS.mdAGENTS.md
- senior-frontendSkill
- vercel-composition-patternsSkill
- bento-designSkill
- fanned-cardsSkill
- flip-cardSkill
- floating-quotesSkill
- githubSkill
- glassmorphism-uiSkill
- gmail-proxySkill
- googleSkill
- hippocampusSkill
- html-pdf-exportSkill
- iframe-previewSkill
- infinite-canvasSkill
- matrix-textSkill
- nextjs-apiSkill
- nextjs-expertSkill
- pinterestSkill
- railway-deploySkill
- remotion-videoSkill
- scramble-textSkill
- scroll-video-heroSkill
- senior-frontendSkill
- SEOSkill
- ship-websiteSkill
- stripe-best-practicesSkill
- tilt-cardSkill
- tube-summarySkill
- upload-postSkill
- vercel-composition-patternsSkill
- vercel-deploySkill
- vercel-react-best-practicesSkill
- vertical-fanned-cardsSkill
- video-contentSkill
- war-roomSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 45
Always create AudioContext lazily (not on mount) to avoid browser autoplay blocks
- Distinctive: line 46
Keep sounds SHORT (20-60ms for clicks, 200-400ms for transitions)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Sound Engine
A complete UI sound design system using the Web Audio API. All sounds are synthesized in real-time with zero external audio files. Provides a React context so any component can trigger sounds.
When to Use
- Premium interactive experiences
- Proposals / pitch sites
- Product demos
- Any UI where tactile feedback adds polish
Sound Library
| Name | Description | Use Case |
tick | Subtle mechanical click | Card hover |
click | Tactile pop with body thud | Button press |
flip | Whoosh + paper snap | Card flip |
slide | Filtered noise sweep | Paper/drawer movement |
crack | Sharp transient + resonance | Breaking/dismissing |
unlock | Rising chime + sparkle | Access granted, success |
tab | Light tap | Tab/nav switch |
reveal | Gentle rising tone | Scroll reveal |
bubble | Wobbly sine wave | Chart interaction |
toggle | Quick square wave click | Sound on/off |
type | Randomized key tap | Typing feedback |
success | C-E-G major chord | Completion |
whoosh | Bandpass noise sweep | Transitions |
Architecture
SoundProvider- wraps app, creates AudioContext lazily on first interactionuseSound()- hook returning{ enabled, toggle, play }SoundToggle- floating button (bottom-right) for on/off- Auto-unlocks AudioContext on user gesture (mobile Safari compatibility)
- Master volume at 0.6, individual sounds mixed for balance
Key Lessons
- Always create AudioContext lazily (not on mount) to avoid browser autoplay blocks
- Keep sounds SHORT (20-60ms for clicks, 200-400ms for transitions)
- Exponential ramps to 0.001 (not 0) to avoid audio pops
- Randomize frequency slightly for repeated sounds (typing) to feel natural
- Sound OFF by default - let users opt in
Reference Implementation
See reference/SoundEngine.tsx for the complete system.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

