{"id":47015,"plugin_id":"plugins_6abdd064e4cc8191bbf9806261446e5d","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:31:53.141Z","digest":"85c6b4d09d107bb9e5c0dba4a0f9eb4f322b5f179aecc4b00c1873d0eff44f1a","against":null,"payload":{"description":"Build a small audio-plugin scaffold, turn an effect idea into a concrete implementation brief, or check build and release evidence. Use Dispro for audio-plugin development and bounded verification, not unrelated media editing.","included_files":[{"relative_path":"references/audio-comparisons.md","size_in_bytes":3438},{"relative_path":"references/engineering-lessons.md","size_in_bytes":9809},{"relative_path":"references/guided-setup.md","size_in_bytes":3775},{"relative_path":"references/parameter-state-contract.md","size_in_bytes":2583},{"relative_path":"references/platform-release-review.md","size_in_bytes":5788},{"relative_path":"references/realtime-safety.md","size_in_bytes":2697},{"relative_path":"references/release-checklist.md","size_in_bytes":4334},{"relative_path":"references/release-gates.md","size_in_bytes":3445},{"relative_path":"references/workflow.md","size_in_bytes":2385},{"relative_path":"scripts/dispro/LICENSE","size_in_bytes":1755},{"relative_path":"scripts/dispro/OUTPUT-LICENSE.txt","size_in_bytes":2522},{"relative_path":"scripts/dispro/__init__.py","size_in_bytes":82},{"relative_path":"scripts/dispro/__main__.py","size_in_bytes":1586},{"relative_path":"scripts/dispro/core.py","size_in_bytes":12388},{"relative_path":"scripts/dispro/templates/gain.c","size_in_bytes":1384},{"relative_path":"scripts/dispro/validate_native.py","size_in_bytes":2091},{"relative_path":"scripts/dispro/vendor/LV2-COPYING","size_in_bytes":827},{"relative_path":"scripts/dispro/vendor/lv2.h","size_in_bytes":24313}],"name":"build-audio-plugin","skill_md_contents":"---\nname: build-audio-plugin\ndescription: Build a small audio-plugin scaffold, turn an effect idea into a concrete implementation brief, or check build and release evidence. Use Dispro for audio-plugin development and bounded verification, not unrelated media editing.\n---\n\n# Dispro\n\nThis release candidate is free to use under the proprietary toolkit LICENSE. Users may modify, distribute and sell generated audio plugins under OUTPUT-LICENSE.txt, including the supplied template material. That permission does not cover modifying or redistributing the reusable toolkit or branding. Preserve upstream notices. Independently authored user work retains its existing rights. Public directory publication remains a separate gate. Support: support@kaizendsp.com.\n\nHelp the user move from an audio-effect idea to a small, reviewable artifact.\nStart with the smallest useful change and reuse already verified results.\nDo not launch extra agents, repeated model calls, CI, paid services, or native\nbuild loops for routine checks. The deterministic scripts need no model API.\n\n## Choose the current deliverable\n\nFor a new effect, start with `references/guided-setup.md`: reuse known answers,\nask only the missing sound/control/target choices, state defaults and show one\ncoherent mockup. Keep the first interaction short. Load the parameter, real-time\nor comparison reference only when that part of the work is needed.\n\nFor a new plugin or DSP design, produce a concise brief and visual mockup first:\nsignal path, channel layout, controls/ranges, state/automation behavior, one\ntarget format/OS and observable acceptance checks. Obtain explicit approval of\nthe mockup before implementing new DSP. Do not interpret approval of a concept\nor another product as approval of this mockup. If image/design tools are absent,\nprovide a clearly labelled wireframe and keep implementation pending approval.\nFor a headless effect, show a control/signal-flow mockup and seek the same approval.\nSee `references/engineering-lessons.md#visual-first` for the handoff.\n\nAn explicit request to exercise the existing mono LV2 gain example may use its\nunchanged recipe directly; this is not a new DSP design. During delivery repairs,\npreserve the product's approved sound/UI. Do not expand a repair into a redesign.\n\nFor a first working artifact, use the original fixed gain recipe in `scripts/`.\nIt is a real LV2 bundle with input, output and a linear 0–2 gain control. It has\nno custom UI, MIDI or state extension. Model-assisted design and code edits\nare a separate phase; v0.1's trusted runner intentionally refuses modified\nrecipes. A new DSP design can be delivered as clearly unverified source and a\nreviewable validation plan, but must not be passed off as a tested recipe.\n\n## Check execution access truthfully\n\nOn ChatGPT web/mobile, provide the brief, source/commands when file tools are\navailable, and a local handoff. An uploaded skill or ZIP does not grant access\nto the user's computer. Do not fabricate a local process, ask for credentials,\ndeploy an execution bridge, or install persistent access. If the current host\noffers an authorized sandbox, distinguish that sandbox from the user's machine.\n\nOn a local Codex/runtime host, use a new dedicated workspace chosen for this\ntask. Do not touch another product checkout, installed plugins, DAWs, global\nsettings, signing keys, or running processes. Use the optional Dispro MCP tools\nonly if already configured; otherwise the bundled CLI works without installing\nanything. Inspect `references/workflow.md` before execution and\n`references/release-gates.md` before claiming release readiness.\nUse `references/release-checklist.md` to review an existing candidate. Consult\nonly the applicable entries in `references/engineering-lessons.md`; these are\ngeneral lessons, not permission to copy product code or a claim of new support.\n\nFor controls/recall, use `references/parameter-state-contract.md`. For a changed\nprocessing path, use `references/realtime-safety.md`. For a sonic change or\nregression, use `references/audio-comparisons.md`: declare the control/tolerance\nfirst, bind exact artifacts and preserve failed comparisons and golden references.\nFor asset staging, platform floors, installers or signing claims, use\n`references/platform-release-review.md`. Separate AAX verification from Windows\npublisher signing, and confirm current publication state and exact approval scope\nbefore any saved-release or public-submission change.\n\n## Run once, record evidence\n\nThe scripts directory is adjacent to this skill. From that directory, run:\n\n```sh\npython3 -m dispro --workspace /absolute/dedicated/dispro-work init\npython3 -m dispro --workspace /absolute/dedicated/dispro-work scaffold first-gain\npython3 -m dispro --workspace /absolute/dedicated/dispro-work run first-gain --timeout 30\n```\n\nSubstitute an actual approved output directory. Never use a user's home,\nrepository root, or another owner's workspace as the output directory.\n`init` refuses nonempty unmarked directories; `scaffold` refuses overwrite.\nUse project slugs, never shell fragments. The CLI needs Python 3.10+ and, for\nnative compilation, macOS/Linux with `/usr/bin/cc`. Windows native build is\nunsupported. Ctrl-C cancels the owned child process group. MCP jobs use\n`cancel_job`; `job_status` reads status without rerunning.\n\nIf the run fails, read its receipt first. Make one focused correction only when\nevidence justifies it. Do not automatically retry builds or change system tools.\nReport stage statuses verbatim: passed, failed or unrun, plus cancelled/timed\nout outcomes. Receipts are local process evidence, not signed attestations.\nSeparate historical evidence, source inspection, mock/syntax fixtures and exact\nnative-host acceptance. Bind each claim to its artifact, dependency identities,\nformat, OS, architecture and named host. Preserve failed evidence and unresolved\ngates; a successful adjacent test cannot replace them. Do not rerun unchanged\nwork solely to accumulate passes.\n\n## Handoff\n\nReturn the scaffold and exact archive location/hash, host/architecture, passed\nchecks, and the next unrun release gate. Offline contract validation is distinct\nfrom DAW discovery, live audio, automation, session recall, signing, notarization\nand publication. Explain SDK/licensing requirements before suggesting another\nformat. Never copy proprietary DSP, branding, credentials, customer data or\nlicence headers from unrelated products into a deliverable.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}