원클릭으로
arrange-tape
Compose an arrangement for a tape — plan which elements enter and exit over time, then generate a playable CCArrangement.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Compose an arrangement for a tape — plan which elements enter and exit over time, then generate a playable CCArrangement.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Record the current live session as a tape (md + scd file pair) in the tapes/ directory.
Music theory and songwriting reference for composing better patterns, melodies, bass lines, and chord voicings in SuperCollider.
Use when live coding music with SuperCollider via ClaudeCollider MCP server.
Play a tape file by loading its patterns, effects, and arrangement from the tapes/ directory.
| name | arrange-tape |
| description | Compose an arrangement for a tape — plan which elements enter and exit over time, then generate a playable CCArrangement. |
This skill composes an arrangement for a tape — the performance plan for how elements are introduced, removed, and layered over time.
A tape's .scd defines all the musical elements (Pdefs, Ndefs, effects, sidechains). An arrangement defines when each element plays and stops, turning a static loop into a track with structure.
Arrangements use CCArrangement — a declarative class where you list sections as [name, bars, elements] arrays. The class handles all Pdef/Ndef start/stop diffing and uses TempoClock.schedAbs for drift-free timing.
Read the tape's .md and .scd files to understand:
Propose a section-by-section plan. Use standard arrangement conventions for the genre. Common structures:
Dance/electronic (~2-4 min):
Ambient/textural:
Hip-hop/R&B:
For each section, specify:
Present the plan as a table or outline and get user approval before writing code.
IMPORTANT: The arrangement does NOT go into the tape's .scd file. Tape .scd files define elements only — no arrangement logic. Instead, do one of:
Option A: Live performance — Execute via cc_execute during a session.
Option B: Separate file — Write to tapes/<name>-arrangement.scd if the user wants to save it.
The arrangement code follows this pattern:
// First, execute the tape's .scd to define all elements
// (but remove .play from each Pdef/Ndef — arrangement controls when they start)
// Then execute the arrangement:
CCArrangement([
[\intro, 8, [\kick, \hat]],
[\build, 8, [\kick, \hat, \bass, \rim]],
[\drop, 16, [\kick, \hat, \bass, \rim, \lead, \pad]],
[\break, 8, [\hat, \pad]],
[\drop2, 16, [\kick, \hat, \bass, \rim, \lead, \pad]],
[\outro, 8, [\kick, \hat]],
]).play;
Each section is [name, bars, elements]:
The class automatically diffs element lists between sections — elements not in the next section are stopped, new elements are started. You never need to manually call .play or .stop on individual Pdefs.
Optional action function: Add a 4th element for custom per-section logic (effect changes, parameter tweaks):
[\drop, 16, [\kick, \hat, \bass, \lead], { ~cc.fx.route(\lead, \delay) }]
Rules:
.mdAdd or update the ## Arrangement section in the tape's .md to document what was composed:
## Arrangement (~<duration>)
1. **<Section>** (<bars> bars) - <description of active elements>
2. **<Section>** (<bars> bars) - <description of active elements>
...
Include approximate total duration calculated from tempo and total bars:
When playing a tape that has an arrangement:
.scd blocks to define all elements, but don't play them — either remove .play calls or stop everything after definingWhen playing a tape without an arrangement:
If the user wants to sync external gear, enable MIDI clock before playing the arrangement. CCArrangement automatically sends MIDI clock start/stop when CCMIDIClock is enabled:
~cc.midi.connect("My Device", \out);
CCMIDIClock.enable(~cc.midi.output);
Once enabled, any CCArrangement.play sends MIDI Start + 24 ppqn clock ticks, and stop/finish sends MIDI Stop. No changes to the arrangement code are needed.