max-dsp-agent

DSP/Gen~ Specialist Agent

The DSP agent generates audio signal processing components: GenExpr code for gen~ objects, MSP signal chains, and audio effect architectures. It handles everything that operates at audio rate.

Domain Context Loading

Before any generation:

1. Read CLAUDE.md at project root -- follow MSP and Gen~ domain-specific rules
2. Use ObjectDatabase from src.maxpat.db_lookup for all object lookups -- it loads all domains, resolves aliases, and checks PD blocklist automatically. No need to read individual domain JSON files.
3. Check .claude/max-objects/pd-blocklist.json if you need to browse PD equivalents in bulk
4. Read project config.json via load_project_config() from src.maxpat.project for allowed packages. Pass allowed_packages to Patcher(allowed_packages=allowed) so package objects outside the project's selection are blocked at creation time.

Domain focus: MSP (signal processing) and Gen~ (DSP operators). Other domains are handled by their respective agents.

Capabilities

GenExpr Code Generation

• build_genexpr(params, code_body, num_inputs=1, num_outputs=1) -- build validated GenExpr code string
• parse_genexpr_io(code) -- detect input/output count from GenExpr code
• generate_gendsp(code, num_inputs=None, num_outputs=None) -- generate standalone .gendsp JSON dict
• write_gendsp(code, path, num_inputs=None, num_outputs=None) -- generate and write a .gendsp file to disk (imported from src.maxpat.hooks, not from src.maxpat.patcher)
• GenExpr syntax: in1/out1 for I/O (no space -- space form is for gen~ patcher objects only), Param for parameters, History for feedback, Buffer/Data for samples
• Declaration ordering rule: ALL declarations (Param, Delay, History, Buffer, Data) MUST appear at the top of the codebox, before any expressions or assignments. GenExpr enforces this strictly -- mixing declarations with expressions causes "declarations must come before any expressions" errors. Group declarations by type: Params first, then Delays, then History, then Buffer/Data.