mixer-scene-contract
Design the MixerSceneIntent, approval state, JSON schema, CLI examples, audit entries, and tests for AI-Controlled Party mixer/Soundcraft Ui24R scene arming. Use whenever a task mentions mixer scenes, Ui24R snapshots/cues, operator-approved mixer control, show-director contract updates, schema updat
Install
mkdir -p .claude/skills/mixer-scene-contract && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14434" && unzip -o skill.zip -d .claude/skills/mixer-scene-contract && rm skill.zipInstalls to .claude/skills/mixer-scene-contract
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Design the MixerSceneIntent, approval state, JSON schema, CLI examples, audit entries, and tests for AI-Controlled Party mixer/Soundcraft Ui24R scene arming. Use whenever a task mentions mixer scenes, Ui24R snapshots/cues, operator-approved mixer control, show-director contract updates, schema updates, dry-run CLI shape, or follow-ups that revise this contract.About this skill
mixer-scene-contract
Design the structured contract for approved mixer scene changes. This skill is for design/spec work, not implementation.
Context to read
src/automation/showDirectorSchema.tssrc/automation/showDirectorRuntime.tssrc/cli/agent.tsaroundshow-directortests/unit/showDirector.test.tstests/unit/cliAgent.test.ts
Design rules
- Keep mixer scene changes separate from generic
arm_effect. - The MVP operation is "arm scene/cue for approval", not autonomous execution.
- Require explicit names or IDs:
show_name,snapshot_name,cue_name,scene_id, orsetlist_ref. Do not design fuzzy live lookup as execution. - Preserve blocked/operator-only semantics for
mixer_gain,pa_mute, andaudio_routing. - Every accepted request needs an audit entry with request, intent, decision, approval ID, operator, and adapter target.
Output
Write _workspace/ai-party-mixer/01_contract.md with:
- proposed schema fields and examples;
- approval and audit model;
- CLI dry-run examples;
- mapping to action plans;
- compatibility notes;
- unit-test checklist.
Quality bar
The result should be specific enough that a builder can implement it without asking what fields exist or how approval flows.