Sound Effects

Announce at start: "I'm using the humane:sound-effects skill to make a small, coherent sound palette for this interface."

Sound is feedback, not wallpaper. Generate a short cue only when it acknowledges a change that the interface needs to make felt: a panel catching after a drag, a confirmed action, a changed mode, or a boundary reached. It is never added merely because something moves.

Before generating

Name the moment and the change it confirms. If the interface already makes it obvious, do not add a sound.
Read the project's token set or DESIGN.md when it exists. It supplies the material vocabulary; do not invent a second brand in audio.
Ask whether sound is opt-in, and identify motion-reduction and system sound settings. Effects must never autoplay, convey the only meaning, or prevent a task from being completed silently.

Generate a palette, not isolated noises

Start with three to five roles. Keep each effect short and quieter than a notification.