Run any Skill in Manus with one click

downspout-add-plugin

Stars5

Forks1

UpdatedJuly 7, 2026 at 12:17

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

danja

danja/downspout

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

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.

Downspout Add Plugin

Use this skill for creating a new plugin or bringing an incomplete plugin into the normal build/release/catalog flow.

First decisions

Identify whether this is an LV2 port or an original plugin.
Identify plugin type: audio effect, MIDI generator/effect, instrument, Launchpad/control plugin, or AI-backed plugin.
Choose a reference plugin with the same shape before writing new code.
Keep the first implementation minimal: portable core, deterministic tests, thin DPF wrapper, then UI.

Required synchronization

When adding a plugin, update all of these in the same change unless the user explicitly scopes the work smaller:

plugin-local CMakeLists.txt with core library, optional DPF target, install rule, and core tests;
root 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;
generated 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.

Implementation shape

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.

More from this repository

same repository

downspout-build-test

danja/downspout

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.

2026-07-175

reaper-compose

danja/downspout

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.

2026-07-125

downspout-extend-plugin

danja/downspout

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.

2026-07-075

downspout-release-catalog

danja/downspout

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.

2026-07-075

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.

Downspout Add Plugin

Use this skill for creating a new plugin or bringing an incomplete plugin into the normal build/release/catalog flow.

First decisions

Identify whether this is an LV2 port or an original plugin.
Identify plugin type: audio effect, MIDI generator/effect, instrument, Launchpad/control plugin, or AI-backed plugin.
Choose a reference plugin with the same shape before writing new code.
Keep the first implementation minimal: portable core, deterministic tests, thin DPF wrapper, then UI.

Required synchronization

When adding a plugin, update all of these in the same change unless the user explicitly scopes the work smaller:

plugin-local CMakeLists.txt with core library, optional DPF target, install rule, and core tests;
root 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;
generated 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.

Implementation shape

Read references/new-plugin-checklist.md for concrete file patterns and validation.