메뉴
Build, test, and verify downspout plugins and core targets. Use when Codex needs to configure CMake, build a plugin or test target, run CTest/core tests, choose narrow verification for a change, or avoid known downspout build-directory races.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Compose, arrange, mix, save, and verify original music in a connected REAPER session through REAPER MCP. Use for requests to create songs, instrumentals, MIDI arrangements, plugin-based productions, or reusable DAW composition recipes, especially when Downspout VST3 instruments and effects are available.
Add a new downspout plugin end to end. Use when Codex is asked to scaffold or port a plugin under the plugins directory and must keep CMake, install, release packaging, docs, screenshots, and GitHub Pages catalog entries synchronized.
Extend or modify behavior in an existing downspout plugin. Use when Codex is asked to add controls, DSP or MIDI behavior, transport/state handling, serialization, UI elements, or tests inside a plugin directory while preserving the portable-core plus thin-DPF-wrapper architecture.
Maintain downspout release packaging, install scripts, GitHub Actions release assets, screenshots, and GitHub Pages plugin catalog metadata. Use when Codex changes plugin bundle lists, adds/removes public plugins, edits docs/pages products, or updates screenshot/release workflows.
| name | downspout-build-test |
| description | Build, test, and verify downspout plugins and core targets. Use when Codex needs to configure CMake, build a plugin or test target, run CTest/core tests, choose narrow verification for a change, or avoid known downspout build-directory races. |
Use this skill whenever validating downspout code changes.
On a fresh CMake build directory, do not start cmake --build until configure has fully completed. This repo can race cache generation and fail with Error: could not load cache if build starts too early.
Before building, check whether the target build directory has CMakeCache.txt:
find build -maxdepth 1 -name CMakeCache.txt -print
If no cache exists, configure first and wait for success:
cmake -S . -B build -DCMAKE_BUILD_TYPE=RelWithDebInfo -DBUILD_TESTING=ON
For a plugin change, usually run:
cmake --build build --target downspout_<plugin_id>_core_tests
./build/plugins/<plugin>/downspout_<plugin_id>_core_tests
cmake --build build --target <bundle_target>
ctest --test-dir build -R downspout_<plugin_id>_core_tests --output-on-failure
Use the plugin-local CMakeLists.txt to confirm exact target names. Hyphenated plugin names often use underscores in C++/test/bundle names, for example p-mix has downspout_p_mix_core_tests and p_mix.vst3.
When a VST3 bundle is rejected by a host, run Steinberg's command-line
validator against the built or installed bundle. Compare with a known-working
Downspout bundle when the output might reflect a DPF-wide limitation.
The locally installed validator is currently:
/home/danny/tools/vst3sdk-build/bin/Release/validator /path/to/plugin.vst3
Treat a signal, non-zero exit status, sanitizer report, or failed test as a
failure even if earlier tests are marked Succeeded. Validator output can be
very large for DPF MIDI plugins, so capture it to a temporary log and search for
Failed, invalid, AddressSanitizer, and the final Result: line.
Read references/commands.md for target naming, useful commands, and validation heuristics.