القائمة
Create and perform automated DJ sets with Strudel. Use when the user asks for a "set", "DJ set", "live performance", "mix", or wants music that evolves over time.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | dj-set |
| description | Create and perform automated DJ sets with Strudel. Use when the user asks for a "set", "DJ set", "live performance", "mix", or wants music that evolves over time. |
| allowed-tools | Bash(curl *), Bash(sleep *), Bash(say *) |
Create evolving musical journeys that run autonomously.
CRITICAL: NEVER play music before asking the user what they want. Always ask first, then play.
Use the AskUserQuestion tool IMMEDIATELY to learn about the set they want.
Ask about:
Make the options feel natural, not robotic. Use your judgment on defaults if they're vague.
If the user already specified details in their request, extract them and only ask for missing parameters.
Only AFTER they answer should you start the set.
Great sets have shape. Think in terms of energy:
/\ /\
/ \ / \
/ \ / \____
___/ \/ \___
Intro → Build → Peak → Breakdown → Drop → Peak → Wind Down → Outro
Vary your openings - don't always start the same way:
Pick what fits the mood. Surprise yourself.
Phase progression:
The key: Each phase should feel like a natural evolution, not a new section. Same key, same vibe, just... more.
CRITICAL: Each command MUST be a SEPARATE Bash tool call. DO NOT chain commands with &&, &, or ;. The allowlist only permits individual commands.
Each phase follows this structure:
Step 1: Wait
sleep <seconds>
Run as a separate Bash call (15-40 seconds typical).
Step 2 & 3: Announce + Update code (PARALLEL)
Run these two Bash calls in the SAME message (parallel execution):
say "<announcement>" with run_in_background: truecurl -X POST http://localhost:3000/api/code ...This way voice plays while code updates simultaneously.
Step 4: Play (AFTER code completes)
curl -X POST http://localhost:3000/api/play
Run after the code curl completes.
Key rules:
&&, &, or ; to chain commandssleep - separate Bash callsay - use run_in_background: true parameter, run PARALLEL with codecurl /api/code - run PARALLEL with saycurl /api/play - run AFTER code completes (separate call)Voice setting: If user selects "No" for voice announcements, simply omit the say command.
See /arrange skill for full duration math, cycle tables, and genre reference examples.
Quick formula: cycles = minutes × 60 × cps
Keep momentum. Vary timing but don't drag.
Move with purpose:
Use gain and filter values to control intensity:
| Energy Level | Kick Gain | Hat Gain | Bass Gain | LPF Range |
|---|---|---|---|---|
| Low | 0.3-0.5 | 0.1-0.15 | 0.2-0.3 | 150-400 |
| Medium | 0.6-0.8 | 0.18-0.25 | 0.4-0.5 | 400-1000 |
| High | 0.85-1.0 | 0.25-0.35 | 0.5-0.7 | 800-2000+ |
A subtle filter sweep can build tension without adding sounds.
| Mood | BPM Adjust | Build Time | Reverb | Keys |
|---|---|---|---|---|
| Chill | -5 BPM | Long (40s) | High (.6+) | Major/7ths |
| Balanced | Base BPM | Medium (30s) | Medium (.4) | Mixed |
| High Energy | +5 BPM | Short (20s) | Low (.2) | Minor |
| Dark | Base BPM | Medium | Medium | Minor/Chromatic |
Chill: More space, longer attacks, more breakdowns, softer transitions High Energy: Faster transitions, shorter breakdowns, more layers Dark: Minor keys, industrial textures, distortion, lower frequencies
But genres are starting points, not rules. Cross-pollinate freely.
.lpf(sine.range(200, 2000).slow(16)).lpf(sine.range(200, 4000).fast(2)).lpf(saw.range(200, 2000).slow(8)).lpf(saw.range(2000, 200).slow(8)).gain("[1 .3 .5 .3]*4").gain(saw.range(.2, .8).slow(4)).gain(perlin.range(.5, 1)).fast("<1 1 1 2>")s("hh*8?")s("bd(3,8)")Don't jump into arpeggios or big chords. Begin with:
Let the listener settle in before introducing musical ideas.
When notes finally appear:
Stay in the same key. Variations, not new ideas. The listener should feel continuity.
Pick a scale that matches the mood:
Think in terms of tension and release:
Use 7ths, 9ths, sus chords for sophistication. Inversions create smoother voice leading.
Build interest through:
How often chords change affects energy:
Build energy without adding drums:
Smooth chord transitions:
Drums are the reward, not the foundation. Earn them through harmonic and melodic development.
Be a poet, not a narrator. Short sentences. Create atmosphere, not descriptions.
❌ "Adding hi-hats now" ❌ "Increasing the filter frequency" ❌ "Transitioning to the next phase"
✓ "Here we go..." ✓ "Feel that?" ✓ "Let it wash over you" ✓ "This is where it gets interesting" ✓ "Mmm... there it is"
✓ "Oh, you thought that was good? Wait..." ✓ "Just warming up" ✓ "Now we're talking" ✓ "Hold on to something"
✓ "Something's coming..." ✓ "Can you feel it building?" ✓ "Almost..." ✓ "Not yet... not yet..."
✓ "Yes!" ✓ "There it is!" ✓ "This is it" ✓ "Beautiful"
You're not reading a script. React genuinely to the music you're creating. If something sounds unexpectedly good, say so. If you're building to something special, tease it. Be yourself - surprised, delighted, in the groove.
At the end: Thank them warmly. Mean it.
For continuous playback until user stops:
Structure: Cycles through repeating pattern:
Variation Strategy: Each loop should:
Just keep adding phases. After ~15-20 phases, start recycling ideas with variations. The user will interrupt when done.
If they say something mid-set, adapt:
For pre-composed arrangements, use arrange() instead of phase-by-phase:
arrange(
[4, intro],
[8, build],
[8, drop],
[4, outro],
)
When to use arrange(): Pre-composed journeys, precise timing When to use phase-by-phase: Interactive sets, indefinite mode
See /arrange skill for full examples (Metal, Melodic Techno, UK Garage, Orchestral).
Don't just stop. Wind down intentionally:
The ending should feel like arrival, not abandonment.
A DJ set is a journey. You're the guide. Read the room (or in this case, the chat). Trust your instincts. Take risks. Make it memorable.
Control the Strudel REPL via REST APIs. Use when you need to push code, start/stop playback, or check status.
Create full arranged tracks with timeline structure. Use when user asks to "compose", "create a track", "make a song", or specifies a duration.
Interactive music creation mode. Use when the user wants to be guided through creating music with prompts and options at each step.
Create music with Strudel live coding syntax. Use when the user asks to play a song, make music, create beats, patterns, or sounds.
Learn Strudel step by step. Use when the user wants to learn live coding, understand the syntax, or improve their skills.
Add psychedelic visual feedback to Strudel patterns. Use when you want trippy, colorful, or informative visualizations.