krate-audio

Domain knowledge for the Gradus step-arpeggiator plugin — the MIDI/event signal path (note input → ArpeggiatorCore → MidiNoteDelay echoes → event out + audition), load-bearing invariants (arp param IDs shared with Ruinae, unified save prefix + intentionally-local load path, fixed event-buffer caps), and where the deep tooling lives. Use when working on Gradus, arpeggiators, the shared arp engine, or Gradus presets — especially outside plugins/gradus/ where the leaf CLAUDE.md won't auto-load.

Guardrailed version bump + release commit for a single Krate Audio plugin. Edits ONLY version.json, adds the matching CHANGELOG entry, then commits — never pushes. Builds and runs that plugin's tests + pluginval only when the tree is not already verified. Use when the user asks to "release", "bump version", "cut a release", or "ship X.Y.Z" for a plugin.

VST3 plugin testing patterns and practices — the broad, general-purpose testing skill. Use when writing tests, debugging test failures, adding new test cases, when tests don't appear after changes, running the test suites, or wiring integration tests. Covers build-before-test discipline, Catch2 patterns and test doubles, integration testing (processor-level wiring, parameter application, host environment), VST3 validation, and anti-patterns. For deep DSP-verification (FFT aliasing measurement, THD/SNR, click/artifact detection, spectral golden references) use the companion testing-dsp-analysis skill.

Domain knowledge for the Innexus harmonic-resynthesis instrument — the analysis→resynthesis signal path, the two analysis front-ends, load-bearing invariants (mono harmonic-sieve, per-partial bandwidth), and where the deep docs live. Use when working on Innexus, harmonic/additive resynthesis, sample or live spectral analysis, or Innexus presets — especially outside plugins/innexus/ where the leaf CLAUDE.md won't auto-load.

DSP and VST3 specialized code review agent. Use to review code changes for real-time safety violations, thread safety issues, numerical stability problems, layer dependency violations, parameter handling bugs, performance concerns, and cross-platform compatibility. Accepts file paths, git diff ranges, or reviews staged/unstaged changes.

Domain knowledge for the Membrum drum-synth plugin — per-voice signal path, preset/kit invariants, ring/range constraints, and where the deep tooling lives. Use when working on Membrum, drum synthesis, kits, pads, bodies/exciters, or Membrum preset retuning, especially outside the plugins/membrum/ tree where the leaf CLAUDE.md won't auto-load.

Deep DSP-verification techniques — FFT-based aliasing measurement, THD/SNR and harmonic analysis, click/LPC/spectral-anomaly artifact detection, frequency estimation, and deterministic test-signal generation. Use ONLY when verifying the numerical/spectral correctness of a DSP algorithm (waveshaper aliasing, oscillator anti-aliasing, saturation THD, click/discontinuity hunting, golden spectral references). For general test writing, Catch2 patterns, build-before-test, integration, and VST3 validation, use the broader testing-guide skill instead.

VST3 SDK and VSTGUI implementation patterns. Use when working on plugin UI, parameter handling, VSTGUI components, editor lifecycle, thread safety, controller code, reusable view templates, sub-controllers, or cross-platform compatibility. Covers parameter types, IDependent pattern, visibility controllers, control selection, template instantiation, tag remapping, and common pitfalls.

DSP development patterns for this VST3 plugin. Use when working on audio processing, dsp/ folder, processors, effects, delay algorithms, filters, or any code that runs on the audio thread. Covers real-time safety, layered architecture, interpolation choices, and performance budgets.

Display the project's main CLAUDE.md file containing all development guidelines, rules, and quick references for this VST3 plugin project.