app-sound-design

license	Apache-2.0
name	app-sound-design
description	Design decisions for when and what sounds to use in web apps, mobile apps, and desktop native apps — plus how to create them with AI. Covers UI sound vocabulary (confirms, alerts, transitions, errors), platform conventions (iOS, macOS, Material), creating sounds with AI tools (ElevenLabs, AudioCraft, Stable Audio), Web Audio API for procedural sounds, haptic-audio pairing, and the psychology of satisfying vs. annoying UI sounds. Activate on 'app sounds', 'UI sounds', 'notification sound', 'sound design app', 'earcons', 'sonic branding', 'interaction sounds', 'feedback sounds', 'app audio', 'satisfying sounds'. NOT for professional audio engineering (use sound-engineer), Windows 3.1 retro sounds specifically (use win31-audio-design), music composition (use sound-engineer).
allowed-tools	Read,Write,Edit,Glob,Grep,WebSearch,WebFetch
metadata	{"category":"Design & UX","tags":["sound-design","UI-sounds","earcons","sonic-branding","Web-Audio-API","haptics","notification","interaction-design","AI-audio"],"pairs-with":[{"skill":"sound-engineer","reason":"Technical audio production when custom sounds need professional post-processing"},{"skill":"win31-audio-design","reason":"Retro sound palettes for themed UIs (WinDAGs, retro games)"},{"skill":"native-app-designer","reason":"Sound decisions are inseparable from native app interaction patterns"},{"skill":"ios-app-beauty","reason":"iOS sound design follows strict Apple HIG conventions"},{"skill":"motion-design-web","reason":"Animation and sound must be synchronized for polished micro-interactions"}]}
category	Design & Creative
tags	["app","sound","design","api","ai","ui"]

App Sound Design

Makes the design decisions about when, what, and how sounds should appear in applications. This is not about audio engineering (that is sound-engineer) or retro sound effects (that is win31-audio-design). This skill answers the hardest question in UI sound: should this interaction make a noise at all? And if yes, what kind?

When to Use

Use for:

• Deciding which interactions in a web or mobile app should have sound feedback
• Selecting appropriate sound characteristics for notifications, confirmations, errors
• Creating AI-generated UI sounds with ElevenLabs, AudioCraft, or Stable Audio
• Implementing procedural sounds with Web Audio API
• Pairing haptic feedback with audio on iOS/Android
• Establishing a sonic brand identity for a product
• Auditing an app's existing sound design for annoyance vs. helpfulness

Do NOT use for:

• Professional audio mixing/mastering -> use sound-engineer
• Windows 3.1 themed system sounds -> use win31-audio-design
• Music composition or soundtrack -> use sound-engineer
• Accessibility screen reader audio -> use accessibility-expert
• Game audio systems (3D positional, dynamic music) -> use sound-engineer

The Fundamental Question: Should This Make a Sound?

Does the interaction need FEEDBACK?
|
+-- User initiated action (tap, click, submit)?
|   +-- Is the result visible on screen?
|   |   +-- YES and obvious --> Sound is OPTIONAL (often skip)
|   |   +-- YES but subtle --> Sound HELPS (gentle confirm)
|   |   +-- NO (background process) --> Sound RECOMMENDED
|   +-- Is the action destructive?
|       +-- YES --> Sound RECOMMENDED (distinct warning tone)
|       +-- NO --> Sound OPTIONAL
|
+-- System initiated event (notification, alert)?
|   +-- Is the user in the app?
|   |   +-- YES --> Subtle in-app sound
|   |   +-- NO --> Notification sound (follow OS conventions)
|   +-- Is it time-sensitive?
|       +-- YES --> More urgent/attention-grabbing sound
|       +-- NO --> Can be silent or ambient
|
+-- Ambient/atmospheric (background state)?
    +-- Does the app benefit from presence? --> Subtle ambient
    +-- Is the user working/focused? --> SILENCE

---

The UI Sound Vocabulary

Every application needs sounds from these categories. Not all categories are required — most apps need 3-5.

Tier 1: Essential (Most Apps Need These)