cdp-wasm-suite/cdp-sound-design

Build, validate, save, share, and preview editable cdp-web patch graphs. Use when the user asks for a cdp-web patch, .cdp file, patch recipe, editable CDP graph, browser-based CDP chain, shareable CDP link, #patch= URL, or wants a CDP sound-design idea opened in the cdp-web frontend rather than only rendered to audio.

Sound design and audio processing with the CDP (Composers Desktop Project) via cdp-wasm. Use whenever the user wants to transform, process, mangle, granulate, time-stretch, pitch-shift, spectrally blur, morph, vocode, reverse, filter, or synthesize audio files; build multi-effect processing chains; batch-process folders of samples; render banks of sound variations; analyse audio (extract a pitch contour or amplitude envelope, detect onsets/peaks) or make one sound follow another's pitch or dynamics; or mentions CDP, phase vocoder / pvoc, granular, spectral, or "sound design" — even if they don't name a specific tool.

Drive a live cdp-web app running in Chrome through its WebMCP agent tools, using the chrome-devtools MCP as the transport. Use whenever the user wants Claude to control, puppeteer, or remote-drive cdp-web in a browser — connect to the cdp-web tab or installed PWA, build or edit a patch live on the canvas, load sounds, set parameters, render, or test the WebMCP tool surface — including phrases like "control the mcp", "drive cdp-web", "build a patch in the browser", or "connect to the cdp-web app". For authoring .cdp files or share links offline (no browser), use build-cdp-web-patches instead; for rendering audio offline via cdp-wasm, use cdp-sound-design.