メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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.
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-add-plugin |
| description | 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. |
Use this skill for creating a new plugin or bringing an incomplete plugin into the normal build/release/catalog flow.
When adding a plugin, update all of these in the same change unless the user explicitly scopes the work smaller:
CMakeLists.txt with core library, optional DPF target, install rule, and core tests;CMakeLists.txt build option and add_subdirectory gate;install.sh build option list;scripts/package-release.sh build option and expected bundle list;.github/workflows/release.yml if release artifact bundle handling is enumerated there;README.md, docs/install.md, docs/release.md, docs/architecture.md, and docs/plan.md where bundle lists or project status change;docs/pages/_products/<plugin>.md with front matter;scripts/capture-plugin-screenshots.sh plugin list and screenshot capture target;docs/pages/assets/plugins/<plugin>.png when UI screenshots are in scope;docs/screenshots.md and docs/pages/README.md if screenshot/catalog processes change.Build the plugin around a portable core first. Do not make the DPF wrapper own the architecture. Add explicit docs for LV2-to-DPF/VST3 mappings, especially transport, state, MIDI ports, and UI behavior.
Read references/new-plugin-checklist.md for concrete file patterns and validation.