max-rnbo-agent

Generate RNBO wrapper patches and validate patch contents for export targets.

41|1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/taylorbrook/MAX-MSP_CC_Framework --skill max-rnbo-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: max-rnbo-agent
Source: https://github.com/taylorbrook/MAX-MSP_CC_Framework/tree/main/.claude/skills/max-rnbo-agent
Command: npx skills add https://github.com/taylorbrook/MAX-MSP_CC_Framework --skill max-rnbo-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many Max/MSP projects need to be exported as VST3/AU plugins, Web Audio modules, or C++ embedded targets but fail at export time due to RNBO incompatibilities, missing parameter mappings, or non-self-contained patch structure. This Skill automates creation and validation of RNBO-ready patch structures, maps GenExpr parameters to RNBO params, and enforces per-target constraints so exports succeed and are production-ready.

Core Features & Use Cases

  • RNBO patch generation: Build rnbo~ containers and full wrapper patches (adc~ -> rnbo~ -> dac~) ready for plugin, web, or C++ export.
  • Target-aware validation: Enforce RNBO_TARGET_CONSTRAINTS, check object compatibility, and verify self-containedness before saving.
  • Param mapping & GenExpr parsing: Extract Param declarations from GenExpr code and create corresponding RNBO parameter objects for host automation.
  • Semantic review & critic: Run critics for naming, duplicate params, and I/O completeness and integrate fixes into the patch.
  • Use Case: Convert an existing GenExpr-based synth into a validated VST3 wrapper with mapped parameters and self-contained resources.

Quick Start

Create an RNBO wrapper patch for a stereo synth targeting VST3, map GenExpr parameters to RNBO params, and run target validation.

Frequently Asked Questions about max-rnbo-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I export a Max/MSP patch as a VST3 plugin using RNBO?

RNBO patch generation builds rnbo~ containers and wrapper patches (adc~ to rnbo~ to dac~) ready for VST3, Web Audio, or C++ export. It ensures object compatibility, validates patch self-containedness, and maps parameters for host automation.

How do I map GenExpr parameters to RNBO params for host automation?

Mapping GenExpr parameters to RNBO params involves extracting Param declarations from GenExpr code and creating corresponding RNBO parameter objects, ensuring the exported plugin responds correctly to host automation controls.

Why does my RNBO patch fail during VST3 or Web Audio export?

RNBO patch exports fail due to RNBO incompatibilities, missing parameter mappings, or non-self-contained patch structures. Target-aware validation enforces per-target constraints, checks object compatibility, and verifies self-containedness to prevent export failures.

Can I use GenExpr code in an RNBO patch for embedded C++ export?

Yes, GenExpr code can be used for embedded C++ export by parsing GenExpr parameters into RNBO params and validating the patch against specific C++ target constraints to ensure object compatibility and self-contained resources.

What's the best way to validate a Max/MSP patch before exporting it as an audio plugin?

The best way to validate a Max/MSP patch before audio plugin export is to run target-aware validation that enforces RNBO constraints, checks object compatibility, performs semantic reviews for duplicate params, and verifies patch self-containedness.