reason-remote-gen
A Claude skill that turns plain-text requests into working MIDI controller mappings for Reason.
Reason's Remote system lets hardware controllers speak directly to devices in the rack (knobs to filter cutoffs, faders to mixer channels, etc) with no manual CC assignment. Mappings follow whichever device has focus. The catch: extending it to a new midi controller or a new plugin means hand-writing tab-delimited .remotemap files and Lua codecs.
What is it?
reason-remote-gen packages the entire domain into a skill file. Remote SDK docs, file-format specs, Remote Info exports from 33+ Reason devices, and a library of working example maps and codecs.
How does it work?
You describe what you want in plain language.
"Generate a remote map for the Novation Launchkey 37 controlling Thor"
"Add a scope block to my existing minilogue remotemap for Europa"
"Create a full codec and remotemap for my DIY 8-encoder controller"
"Map my Akai MPK mini mk3 to Kong in Reason 13"
Claude asks for anything it's missing (device ID, parameter names, control layout) and generates production-ready files with installation instructions.
Export Files
reason-remote-gen produces three file types, each with a distinct job:
.remotemap: the mapping layer. Routes your controller's knobs, faders, and buttons to specific device parameters, with scope blocks per device. If Reason already supports your controller, this is all you need.
.lua codec: the behavior layer. Defines the controller itself: what controls it has, what MIDI it sends, and how values are interpreted.
.luacodec: the registration file that makes a new controller appear in Reason's control surface preferences.
Supported targets
Native Reason devices: Subtractor, Thor, Kong, Europa, Grain, and the rest of the stock rack
Rack Extensions: any RE that supports Remote Info export
VST/VST3 plugins loaded in Reason