# mpc-plugin-ui

The mpc-plugin-ui Claude Code skill builds touch-screen layouts and Q-Link mappings for MPC plugins. It comes into play when an agent needs to arrange controls, set themes, or create a custom skin.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 200 repo stars
- Author: inmusic-software
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/inmusic-software/mpc-plugin-builder-sdk/tree/HEAD/.claude/skills/mpc-plugin-ui/SKILL.md
- Updated: 2026-11-07
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/mpc-plugin-ui

## What it does

The skill helps build an MPC plugin interface with `ui.json` or hand-authored `TUI.json` and `Q-Links.json` files. The simpler route uses the SDK’s UI kit and `tools/build.py`; parameter names come from `build/params.json` after a native build. Layouts can include pages, knobs, faders, switches, labels, themes, and controls that appear only for selected parameter values.

The full format allows custom images and precise placement. MPC checks object versions and required JSON keys; a mismatch can remove every plugin tab. Run `python tools/validate.py plugins/<Name>` after editing. Building and validation require Python and the SDK files; the manual format also relies on correct parameter and tab indices.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-ui -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/mpc-plugin-ui/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/mpc-plugin-ui/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-ui -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/mpc-plugin-ui/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-ui -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/mpc-plugin-ui/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install inmusic-software/mpc-plugin-builder-sdk .claude/skills/mpc-plugin-ui
```

2. **Manually: put the files in place**
- File: `.github/skills/mpc-plugin-ui/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-ui -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/inmusic-software/mpc-plugin-builder-sdk --path .claude/skills/mpc-plugin-ui
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/mpc-plugin-ui/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/inmusic-software/mpc-plugin-builder-sdk/tree/HEAD/.claude/skills/mpc-plugin-ui/SKILL.md

## When to use it
- arrange plugin parameters across MPC pages
- map Q-Link controls to knobs and faders
- show a control only for selected parameter values
- build a skin with custom images

## Example prompts
- Arrange this MPC plugin’s parameters into pages with `ui.json`.
- Set up Q-Link mappings for this plugin’s knobs and faders.
- Create a hand-authored skin with `TUI.json` and `Q-Links.json`.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 3331931bf4b22c8e.

BEGIN THIRD-PARTY FILE 3331931bf4b22c8e
````text
---
name: mpc-plugin-ui
description: Design or change an MPC plugin's touch-screen UI and hardware knob (Q-Link) mapping, via the simple ui.json layout (film-strip knobs, faders and switches from the SDK's UI kit) or the full Plugin Skins JSON format (TUI.json, Q-Links.json). Use when the user wants pages, knobs, faders, switches, layout, labels, themes, conditional controls, images or custom skins for their plugin.
---

# Plugin UI on the MPC

The MPC draws plugin UIs from JSON skins in `Plugin Skins/`. Two ways to produce them. Use A unless the user asks for something it cannot do.

## A. The simple way: `ui.json` with the UI kit (default)

Edit `plugins/<Name>/ui.json`; `tools/build.py` turns it into the skin files. Full format: `docs/ui-guide.md`; schema: `schemas/ui.schema.json`. **Always give every parameter a real widget (`knob`, `fader` or `switch`) rather than the generic `slider`**; the generic bar is a fallback for long choice lists only. The kit graphics live in `ui-kit/` (look at `ui-kit/preview.png`; `ui-kit/README.md` explains them).

```json
{ "kit": "mpc-red",
  "pages": [ { "name": "FILTER", "controls": [
      { "param": "Cutoff",  "widget": "knob" },
      { "param": "Reso",    "widget": "knob" },
      { "param": "Mode",    "widget": "switch" },
      { "param": "Env Amt", "widget": "knob", "polarity": "bipolar" },
      { "param": "Attack",  "widget": "fader" }, { "param": "Decay", "widget": "fader" },
      { "param": "Sustain", "widget": "fader" }, { "param": "Release", "widget": "fader" },
      { "param": "Shape",   "widget": "slider", "overlay": "menu" },
      { "param": "Rate",    "widget": "knob", "visibleWhen": { "param": "Sync", "choice": "Off" } },
      "empty", { "widget": "text", "text": "Modulation" } ] } ] }
```

- Controls are parameter **names** exactly as declared in code (not ids). `build/params.json` lists them after a native build.
- ≤ 16 controls per page, reading order into a 4 × 4 grid that matches the 16 hardware knobs. The MPC itself does not require a grid (hand-written skins place controls freely), but the knobs work in **groups of four** and the focus rectangle wraps a group, so arrange controls as blocks of four (a row of four or a column of four; Q-Link groups can be horizontal or vertical). Each block should be one coherent set, so the interface looks intentionally aligned; page names ≤ 8 characters; ≤ 32 pages.
- Widgets: `knob`, `fader`, `switch` (kit), `slider` (generic bar), `text`, `empty`. `polarity` (`auto` / `unipolar` / `bipolar`) on knobs and faders. `overlay: "menu"` for long choice lists. `visibleWhen` shows a control only for a given choice/bool value.
- `kit`: `mpc-red` (default), `amber`, `cyan`, `lime`, `violet`, `mono`, or `{ "theme": "...", "accent": "AARRGGBB" }`. One theme per plugin. The build renders it (cached in `build/`) and copies only the PNGs the layout uses.
````
END THIRD-PARTY FILE 3331931bf4b22c8e

The third-party file has ended. Everything between the 3331931bf4b22c8e tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2899 of 6959 bytes. © inmusic-software · MIT · https://github.com/inmusic-software/mpc-plugin-builder-sdk/tree/HEAD/.claude/skills/mpc-plugin-ui/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
