agentsclimarketplace

Interface sound

Skill tommylower/cortex/design/motion/interface-sound

Public skill library, workflows, tools, and references for AI-assisted development.

Install
npx -y skills add tommylower/cortex --skill interface-sound

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Design and implement tasteful interface sound for web apps using @web-kits/audio or Web Audio. Use when the user asks for UI sounds, sound effects, audio feedback, button clicks, success tones, error tones, notification sounds, procedural audio, sound patches, or wants to audit whether sound belongs in an interface.

SKILL.md

3.1 KB, as published. Nobody here has run it

Interface Sound

Use sound as interaction feedback, not decoration. Sound should clarify state, confirm rare actions, or make a product moment more legible.

Sources:

When Sound Belongs

Use sound for:

  • success or completion moments
  • error, warning, or destructive feedback
  • notification or mention events
  • tactile controls in creative tools, games, and playful apps
  • onboarding or first-run moments where feedback is part of the product feel

Avoid sound for:

  • high-frequency hover states
  • normal navigation
  • dense productivity workflows unless the user opted in
  • anything that could fire repeatedly in a loop

Accessibility & UX Rules

  • Default to muted or low volume unless the product category implies sound.
  • Provide a visible sound setting when sounds can repeat or persist.
  • Never autoplay sound on page load.
  • Initialize audio from a user gesture.
  • Respect reduced-motion style preferences as a signal to keep sensory feedback restrained.
  • Pair every sound with visual feedback; sound must never be the only state indicator.

Install

bun add @web-kits/audio
pnpm add @web-kits/audio
npm install @web-kits/audio

Basic Pattern

import { defineSound, ensureReady } from "@web-kits/audio";

const successTone = defineSound({
  source: { type: "sine", frequency: { start: 660, end: 880 } },
  envelope: { attack: 0.005, decay: 0.12, release: 0.04 },
  gain: 0.18,
});

export async function playSuccessTone() {
  await ensureReady();
  successTone();
}

Call from an intentional user action, such as a completed submit or confirmed command.

Sound Vocabulary

EventDirection
click / tapvery short, low gain, fast decay
toggle ontwo small ascending tones
toggle offtwo small descending tones
successsoft ascending interval or small chord
errorshort descending tone, restrained distortion
notificationclear but quiet bell-like tone
modal opensubtle ascending whoosh
modal closeshorter descending whoosh

Implementation Notes

  • Keep per-sound gain conservative; start around 0.12 to 0.25.
  • Keep most UI sounds under 200ms.
  • Use patches when a project has more than a couple sounds.
  • Store reusable patches under .web-kits/ or a project-specific src/sounds/ directory.
  • Add a single sound preference in app settings before adding many sounds.

Verification

Before shipping:

  1. Confirm sound only plays after user interaction.
  2. Confirm mute/off works.
  3. Test repeated actions for annoyance.
  4. Test with system volume high.
  5. Confirm the same state is visible without sound.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.