max-ext-agent

To scaffold a C++ Max external, the skill generates a full Min-Devkit project structure for message, DSP, or scheduler objects, producing archetype-specific C++ source ready for compilation.

Yes, you can automate the build process for .mxo bundles by running cmake and make loops with error parsing and auto-correction, attempting to fix compilation issues up to five times automatically.

Mach-O validation for Max externals checks the resulting .mxo bundle to ensure it has the correct Mach-O type and arm64 architecture, confirming the external is structurally ready for Max/MSP.

The best way to generate a help patch is to automatically build demonstration .maxhelp patches for the new external, providing a visual interface to test the object directly within Max/MSP.

You need cmake and make to compile C++ externals for Max/MSP because the skill leverages these tools in automated build loops to parse errors and auto-correct compilation failures for .mxo bundles.

C++ Max externals fail to build due to boilerplate or structural code issues, which a critic review catches, while automated cmake/make loops parse errors and auto-correct compilation up to five attempts.