Plan → generate → fix
Big generations shouldn't be a slot machine. Splitting the work into a cheap planning stage and an expensive build stage means you spend the real tokens only on a scene you've already read and approved.
AI · Plugins
An entire plugin, planned then built.
The most ambitious generator in Visualz: describe a source or effect and get a complete, installable plugin bundle. It works in stages — you approve an editable plan before any code is written, and a dedicated fix pass repairs runtime errors after.
1 · Plan
Describe the source or effect you want. The generator returns an editable scene plan — name, summary, up to 12 params, up to 8 audio reactions, and the permissions it wants. Nothing is built yet; reshape the plan until it’s right.
2 · Generate
Approve the plan and the generator writes the whole bundle — manifest plus code — as a real plugin that hot-loads into the live scene like any hand-written one.
3 · Fix
If a generated plugin errors at runtime, feed the error back — optionally with a screenshot for visual bugs — and the fix pass repairs the code against the original plan.
Permissions, declared up front
Plugins run sandboxed, and generated ones are no exception. The plan declares exactly which capabilities the plugin wants — camera, microphone, network, MIDI, filesystem, or library access — and you see the list before generating and again at install.
Checked against the sandbox before it ships
Every generated bundle is statically scanned server-side against the same rules the renderer sandbox enforces — no escape hatches, no forbidden globals, a clean plugin entry point. Output that fails the scan is rejected and refunded rather than delivered broken.
Tokens: ~2300 for a full plugin generation; the plan and fix passes are metered separately and cost far less. Rejected or failed generations refund in full.