Review UI code for audio feedback best practices and accessibility.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsounds-on-the-webExecute the skills CLI command in your project's root directory to begin installation:
Fetches sounds-on-the-web from raphaelsalaja/userinterface-wiki and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate sounds-on-the-web. Access via /sounds-on-the-web in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
684
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
684
stars
Review UI code for audio feedback best practices and accessibility.
file:line format| Priority | Category | Prefix |
|---|---|---|
| 1 | Accessibility | a11y- |
| 2 | Appropriateness | appropriate- |
| 3 | Implementation | impl- |
| 4 | Weight Matching | weight- |
a11y-visual-equivalentEvery 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-settingProvide 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-checkRespect 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-controlAllow 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();
}
appropriate-no-high-frequencyDo 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-onlySound is appropriate for confirmations: payments, uploads, form submissions.
Pass:
async function handlePayment() {
await processPayment();
playSound("success"); // Appropriate - significant action
showConfirmation();
}
appropriate-errors-warningsSound 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-decorativeDo 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-punishingSound 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>;
}
impl-preload-audioPreload
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
supercent-io/skills-template
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
sounds-on-the-web has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend sounds-on-the-web for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: sounds-on-the-web is the kind of skill you can hand to a new teammate without a long onboarding doc.
sounds-on-the-web fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for sounds-on-the-web matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in sounds-on-the-web — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: sounds-on-the-web is focused, and the summary matches what you get after install.
Registry listing for sounds-on-the-web matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: sounds-on-the-web is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added sounds-on-the-web from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 41