By danielraffel
Build, test, debug, and ship audio plugins and apps with the Pulp framework, including cross-platform builds, DSP validation, UI prototyping, CI automation, and release packaging
Prove and inspect what a Pulp processor emits — run the audio observability harness (metrics, scenarios, contracts) and the offline Audio Doctor analyzers (frequency response, THD)
Open the developer Audio Inspector window — live meters, probe-stage status, copied waveform, L/R level-match + balance, and a device/runtime summary
Onboard a Mac as a Tart-VM CI host (optional; wraps setup-ci-host.sh)
Connect to a running Pulp inspector server
Search, inspect, plan, approve, and apply local Pulp kit manifests or `.pulpkit` archives.
Optional AAX support for Pulp, including developer-supplied Avid SDK setup, CMake enablement, DigiShell/AAX Validator workflows, and local AAX builds on macOS or Windows.
Android platform development for Pulp — NDK cross-compilation, Oboe audio, Dawn/Skia GPU rendering, JNI bridge, touch interaction, emulator workflows, end-to-end smoke validation (#337). Covers build, deploy, debug, and the gotchas discovered during bringup.
Optional ARA support for Pulp, including developer-supplied ARA SDK setup, CMake enablement, adapter companion APIs, validation, and ARA-aware plugin implementation guidance.
Prove and debug what a Pulp processor actually emits — the audio observability harness (signal generators, metrics, assertions, RenderScenario, effect contracts) plus the offline Audio Doctor analyzers (magnitude/frequency response, THD/THD+N). TRIGGER on phrases like "is there sound / no audio / I hear nothing", "does this filter/compressor/synth/delay produce the right signal", "prove the DSP / prove the contract", "measure the frequency response", "what's the THD / is it distorting / aliasing", "render a test tone and assert", "audio regression", "64-frame works but 128 is silent", "sample-rate change pitch-shifted it", "describe what's in this buffer", "audio doctor", "magnitude response curve", "compare before/after a DSP refactor". Test/tool layer over HeadlessHost — deterministic, no audio device, no speakers. Off the realtime thread entirely.
Reproduce and debug "only happens in a DAW" audio plugin bugs (cutouts, glitches, parameter-change failures) entirely offline — headless Processor scenes for DSP bugs and a standalone AudioUnit host probe for adapter/host-interaction bugs. Use when a plugin misbehaves in Logic/Live/etc. but unit tests are green.
Modifies files
Hook triggers on file write and edit operations
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A cross-platform audio plugin and application framework. MIT licensed, C++20 core, Swift on Apple, JS-scripted GPU UIs.
curl -fsSL https://www.generouscorp.com/pulp/install.sh | sh
Then:
pulp create my-plugin && cd my-plugin && pulp run
Three commands from zero to a working plugin in all formats.
The CLI works great with any AI coding agent (Claude, Codex, Cursor). If you use Claude Code, you can additionally install the Pulp plugin for slash-command shortcuts (/build, /test, /ship) and a native MCP server:
claude plugin marketplace add danielraffel/pulp && claude plugin install pulp
Install the CLI first. The plugin's MCP server is
pulp-mcp, which ships with the CLI tarball (above) into~/.pulp/bin/. The plugin itself contains no binaries — it locatespulp-mcpon$PATH. If you install the plugin before runninginstall.sh,/mcpwill reportpulp-mcp: cannot locate binary. Runpulp doctorto confirmpulp-mcpis found and matches your CLI version.(Building from a source checkout instead? The repo's project-local MCP server uses the binary from your build tree — see Build from source. No CLI install needed.)
See docs/agent-integrations.md for details on each agent path.
Plugin Formats
Create & Build
pulp create scaffolds a full plugin project with all format targetspulp build builds all formats in one passpulp test runs the local test suite (ctest over the project's build directory); cross-platform execution and coverage roll up to CI — coverage is tracked at codecov.io/gh/danielraffel/pulppulp run launches standalone for quick iterationpulp doctor checks your environment and reports missing dependenciesUI & Design
matchMedia queriespulp design) for generating UIs from promptsDSP & Audio
Rendering
Shipping
pulp ship sign, pulp ship package, pulp ship checkCI & Automation
Platform Support
npx claudepluginhub danielraffel/pulp --plugin pulpAI-powered design thinking partner that helps explore ideas, generate visuals, and create prototypes through natural conversation
Generate agent team orchestration prompts from any task description
Create and manage JUCE audio plugin projects from the JUCE-Plugin-Starter template
Apply Google Research's prompt repetition technique to improve LLM performance on non-reasoning tasks
Cross-platform CI coordination
20 SEO/GEO skills and 5 commands on one shared contract for keyword research, content creation, technical audits, schema markup, monitoring, quality gates, entity truth, and campaign memory.
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use
Modern R development skills for Claude Code - tidyverse patterns, rlang metaprogramming, Bayesian inference, performance optimization, and more
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Unity Development Toolkit - Expert agents for scripting/refactoring/optimization, script templates, and Agent Skills for Unity C# development