What problem does it solve? Procedural audio code written with the Web Audio API often contains subtle mistakes—leaked AudioContext instances, linear ramps that sound unnatural, exponential ramps targeting zero, or poorly tuned filter parameters—that produce glitches, harsh tones, or memory leaks. This Skill reviews that code against a defined rule set and reports each violation with an exact file and line number. ## Core Features & Use Cases - Rule-Based Auditing: Checks code against 13 rules across four categories: context management, envelope/decay, sound design, and parameter ranges. - Structured Findings: Outputs violations in file:line - [rule-id] description format plus a severity summary table. - Parameter Translation: Maps subjective feedback like "too harsh" or "too muffled" to concrete parameter changes such as filter frequency, Q value, or decay curve. - Use Case: A developer implementing UI click and confirmation sounds asks for a review of lib/sounds.ts and receives findings like lib/sounds.ts:23 - [envelope-exponential-decay] Using linearRampToValueAtTime instead of exponential. ## Quick Start Review the Web Audio API sound code in my project and report any violations of sound synthesis best practices with file and line numbers.