
Sounds On The Web
- 127 installs
- 32 repo stars
- Updated March 17, 2026
- raphaelsalaja/skill
Sounds on the Web is an agent skill that audits UI code for audio feedback accessibility and UX, emitting file:line findings.
About
Sounds on the Web is an agent skill for solo builders shipping interactive web or app UIs who add subtle audio feedback without breaking accessibility or annoying users. It reads specified source files—or asks you for paths—then audits against prioritized rule categories spanning accessibility (visual equivalents, disable toggles), whether sound is appropriate for the action, implementation quality, and matching sonic weight to UI importance. Findings land as file:line citations you can paste into fixes. Use it during code review before ship, when refactoring notification or game-like micro-interactions, or when validating that sound never replaces visible state changes. It complements visual design review rather than replacing sound design tooling.
- Four rule categories with priority order: accessibility, appropriateness, implementation, weight matching
- Outputs findings in file:line format for direct fixes in the repo
- Accessibility rules: visual equivalent for every cue, explicit sound toggle in settings
- Covers appropriateness, implementation patterns, and weight-matching for UI sounds
- MIT-licensed audit workflow—read files or prompt for paths, then check all rules
Sounds On The Web by the numbers
- 127 all-time installs (skills.sh)
- +9 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #1,001 of 2,245 Frontend Development skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/raphaelsalaja/skill --skill sounds-on-the-webAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 127 |
|---|---|
| repo stars | ★ 32 |
| Security audit | 3 / 3 scanners passed |
| Last updated | March 17, 2026 |
| Repository | raphaelsalaja/skill ↗ |
What it does
Review UI code for sound-effect UX and accessibility so every audio cue has visual parity, user controls, and appropriate weight.
Who is it for?
Best when you're reviewing React or similar components that call playSound or Web Audio before a release.
Skip if: Composing sound libraries, mixing mastering, or backend-only APIs with no client audio code to inspect.
When should I use this skill?
Reviewing sound implementation, checking audio UX decisions, or auditing accessibility of UI audio feedback in code.
What you get
You receive prioritized file:line audit results across four rule categories so you can fix audio UX before users ship with silent failures or a11y gaps.
- Prioritized file:line findings per rule prefix (a11y-, appropriate-, impl-, weight-)
By the numbers
- 4 prioritized rule categories: accessibility, appropriateness, implementation, weight matching
- Findings reported in file:line format
- Skill version 2.0.0 per metadata
Files
Sounds on the Web
Review UI code for audio feedback best practices and accessibility.
How It Works
1. Read the specified files (or prompt user for files/pattern) 2. Check against all rules below 3. Output findings in file:line format
Rule Categories
| Priority | Category | Prefix |
|---|---|---|
| 1 | Accessibility | a11y- |
| 2 | Appropriateness | appropriate- |
| 3 | Implementation | impl- |
| 4 | Weight Matching | weight- |
Rules
Accessibility Rules
a11y-visual-equivalent
Every audio cue must have a visual equivalent; sound never replaces visual feedback.
Fail:
function SubmitButton({ onClick }) {
const handleClick = () => {
playSound("success");
onClick(); // No visual confirmation
};
}Pass:
function SubmitButton({ onClick }) {
const [status, setStatus] = useState("idle");
const handleClick = () => {
playSound("success");
setStatus("success"); // Visual feedback too
onClick();
};
return <button data-status={status}>Submit</button>;
}a11y-toggle-setting
Provide explicit toggle to disable sounds in settings.
Fail:
// No way to disable sounds
function App() {
return <SoundProvider>{children}</SoundProvider>;
}Pass:
function App() {
const { soundEnabled } = usePreferences();
return (
<SoundProvider enabled={soundEnabled}>
{children}
</SoundProvider>
);
}a11y-reduced-motion-check
Respect prefers-reduced-motion as proxy for sound sensitivity.
Fail:
function playSound(name: string) {
audio.play(); // Plays regardless of preferences
}Pass:
function playSound(name: string) {
const prefersReducedMotion = window.matchMedia(
"(prefers-reduced-motion: reduce)"
).matches;
if (prefersReducedMotion) return;
audio.play();
}a11y-volume-control
Allow volume adjustment independent of system volume.
Fail:
function playSound() {
audio.volume = 1; // Always full volume
audio.play();
}Pass:
function playSound() {
const { volume } = usePreferences();
audio.volume = volume; // User-controlled
audio.play();
}Appropriateness Rules
appropriate-no-high-frequency
Do not add sound to high-frequency interactions (typing, keyboard navigation).
Fail:
function Input({ onChange }) {
const handleChange = (e) => {
playSound("keystroke"); // Annoying on every keystroke
onChange(e);
};
}Pass:
function Input({ onChange }) {
// No sound on typing - visual feedback only
return <input onChange={onChange} />;
}appropriate-confirmations-only
Sound is appropriate for confirmations: payments, uploads, form submissions.
Pass:
async function handlePayment() {
await processPayment();
playSound("success"); // Appropriate - significant action
showConfirmation();
}appropriate-errors-warnings
Sound is appropriate for errors and warnings that can't be overlooked.
Pass:
function handleError(error: Error) {
playSound("error"); // Appropriate - needs attention
showErrorToast(error.message);
}appropriate-no-decorative
Do not add sound to decorative moments with no informational value.
Fail:
function Card({ onHover }) {
return (
<div onMouseEnter={() => playSound("hover")}> {/* Decorative, no value */}
{children}
</div>
);
}appropriate-no-punishing
Sound should inform, not punish; avoid harsh sounds for user mistakes.
Fail:
function ValidationError() {
playSound("loud-buzzer"); // Punishing
return <span>Invalid input</span>;
}Pass:
function ValidationError() {
playSound("gentle-alert"); // Informative but not harsh
return <span>Invalid input</span>;
}Implementation Rules
impl-preload-audio
Preload audio files to avoid playback delay.
Fail:
function playSound(name: string) {
const audio = new Audio(`/sounds/${name}.mp3`); // Loads on demand
audio.play();
}Pass:
const sounds = {
success: new Audio("/sounds/success.mp3"),
error: new Audio("/sounds/error.mp3"),
};
// Preload on app init
Object.values(sounds).forEach(audio => audio.load());
function playSound(name: keyof typeof sounds) {
sounds[name].currentTime = 0;
sounds[name].play();
}impl-default-subtle
Default volume should be subtle, not loud.
Fail:
const DEFAULT_VOLUME = 1.0; // Too loudPass:
const DEFAULT_VOLUME = 0.3; // Subtle defaultimpl-reset-current-time
Reset audio currentTime before replay to allow rapid triggering.
Fail:
function playSound() {
audio.play(); // Won't replay if already playing
}Pass:
function playSound() {
audio.currentTime = 0;
audio.play();
}Weight Matching Rules
weight-match-action
Sound weight should match action importance.
Fail:
// Loud fanfare for minor action
function handleToggle() {
playSound("triumphant-fanfare");
setEnabled(!enabled);
}Pass:
// Subtle click for minor action
function handleToggle() {
playSound("soft-click");
setEnabled(!enabled);
}
// Richer sound for significant action
function handlePurchase() {
playSound("success-chime");
completePurchase();
}weight-duration-matches-action
Sound duration should match action duration.
Fail:
// 2-second sound for instant action
function handleClick() {
playSound("long-whoosh"); // 2000ms
// Action completes immediately
}Pass:
// Short sound for instant action
function handleClick() {
playSound("click"); // 50ms
}
// Longer sound for process
function handleUpload() {
playSound("upload-progress"); // Matches upload duration
}Output Format
When reviewing files, output findings as:
file:line - [rule-id] description of issue
Example:
components/input/index.tsx:23 - [appropriate-no-high-frequency] Playing sound on every keystroke
lib/sounds.ts:45 - [a11y-reduced-motion-check] Not checking prefers-reduced-motionSummary Table
After findings, output a summary:
| Rule | Count | Severity |
|---|---|---|
a11y-visual-equivalent | 2 | HIGH |
appropriate-no-high-frequency | 1 | HIGH |
impl-preload-audio | 3 | MEDIUM |
Sound Appropriateness Matrix
| Interaction | Sound? | Reason |
|---|---|---|
| Payment success | Yes | Significant confirmation |
| Form submission | Yes | User needs assurance |
| Error state | Yes | Can't be overlooked |
| Notification | Yes | May not be looking at screen |
| Button click | Maybe | Only for significant buttons |
| Typing | No | Too frequent |
| Hover | No | Decorative only |
| Scroll | No | Too frequent |
| Navigation | No | Keyboard nav would be noisy |
References
Related skills
How it compares
A focused UI sound checklist reviewer—not a general lighthouse audit or DAW workflow.
FAQ
Who is sounds-on-the-web for?
Developers and small teams shipping web or hybrid apps who implement optional UI sounds and need a systematic code review pass.
When should I use sounds-on-the-web?
Use when reviewing sound implementation in Ship review, auditing accessibility of audio cues, or checking UX decisions during Build frontend polish.
Is sounds-on-the-web safe to install?
It is a read-only review skill over your codebase; confirm repo trust and review the Security Audits panel on this page before running agents on production code.