agentleFS
renatoworksrenatoworks/strudel-claude/.claude/skills/dj-set/SKILL.md

dj-set

Skill61 starsChanged 10 months agoMITView on GitHub

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.

  • Sends data out

The file

Show its rules and text

We split this skill into the rules it gives an agent

28 rules. About 0 are common, 26 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈26

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create evolving musical journeys that run autonomously.

    line 9
  2. Distinctive:

    CRITICAL: NEVER play music before asking the user what they want.

    line 15
  3. Distinctive:

    Voice: - Should you announce transitions?

    line 23
  4. Distinctive:

    If the user already specified details in their request, extract them and only ask for missing parameters.

    line 27
  5. Distinctive:

    Only AFTER they answer: should you start the set.

    line 29
  6. Distinctive:

    Audible from the start: - not a whisper, but gentle

    line 47
  7. Distinctive:

    Avoid harsh jumps in volume or density

    line 94
  8. Distinctive:

    Run as a separate Bash call (15-40 seconds typical).

    line 124
  9. Distinctive:

    Run these two Bash calls in the SAME message (parallel execution):

    line 128
  10. Distinctive:

    Run after the code curl completes.

    line 138
  11. Very specific:

    NEVER use &&, &, or ; to chain commands

    line 141
  12. Very specific:

    Voice setting: If user selects "No" for voice announcements, simply omit the say command.

    line 147
  13. Distinctive:

    Don't linger too long before things start happening

    line 165
  14. Distinctive:

    NEVER make harsh transitions: - no sudden jumps in energy, volume, or density

    line 187
  15. Distinctive:

    Every change should flow naturally from what came before

    line 188
  16. Distinctive:

    Use gain and filter values to control intensity:

    line 194
  17. Distinctive:

    Don't jump into arpeggios or big chords.

    line 286
  18. Distinctive:

    When notes finally appear:

    line 294
  19. Distinctive:

    Start with 2-3 notes - a motif, not a melody

    line 295
  20. Distinctive:

    Use 7ths, 9ths, sus chords for sophistication.

    line 318
  21. Distinctive:

    Range expansion: - start narrow, open up over time

    line 326
  22. Distinctive:

    Add harmonics (5ths, octaves)

    line 340
  23. Distinctive:

    Use inversions to keep bass movement stepwise

    line 347
  24. Distinctive:

    If they say something mid-set, adapt:

    line 427
  25. Distinctive:

    Patience: - Don't rush transitions. Let each phase breathe.

    line 438
  26. Distinctive:

    Movement: - Every phase should have SOMETHING moving (filter, gain, etc.)

    line 441
  27. Distinctive:

    Don't just stop. Wind down intentionally:

    line 469
  28. Distinctive:

    If voice is on, thank them

    line 473

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

DJ Set Mode

Create evolving musical journeys that run autonomously.


Before Starting

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:

  • Genre/vibe - What world are we in?
  • Length - Quick taste or full journey?
  • Mood - Chill, driving, dark, euphoric?
  • Voice - Should you announce transitions?

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.


Set Structure (The Arc)

Great sets have shape. Think in terms of energy:

      /\      /\
     /  \    /  \
    /    \  /    \____
___/      \/          \___

Intro → Build → Peak → Breakdown → Drop → Peak → Wind Down → Outro

1. INTRO (1-2 phases)

  • Audible from the start - not a whisper, but gentle
  • Set the tone - could be anything that fits the vibe
  • Some filtering, but not buried

Vary your openings - don't always start the same way:

  • Soft percussion (hats, shakers, rim clicks)
  • A warm pad or drone
  • Filtered melodic loop
  • Atmospheric texture or noise
  • A single repeated note
  • Sparse piano or keys

Pick what fits the mood. Surprise yourself.

2. BUILD (5-7 phases)

  • Gradually introduce musical elements
  • Each phase adds ONE thing
  • Stay in the same key throughout
  • Variations, not new ideas

Phase progression:

  1. First notes appear - sparse, simple (2-3 notes max)
  2. Notes become a phrase - still simple
  3. Chords enter softly - just pads, filtered
  4. Bass joins - following the harmony
  5. Melody emerges - built from earlier notes
  6. Kick enters (finally!) - filtered, subtle
  7. Elements open up - filters rise, groove establishes

The key: Each phase should feel like a natural evolution, not a new section. Same key, same vibe, just... more.

3. FIRST PEAK (2-3 phases)

  • Full groove established
  • All elements present
  • Filter sweeps for movement

4. BREAKDOWN (1-2 phases)

  • Strip back to minimal elements
  • Atmospheric, tension-building
  • Just pads, sparse kick, maybe melody
  • Creates anticipation

5. THE DROP (1-2 phases)

  • Smooth transition, not a slap
  • Elements return gradually, not all at once
  • Maybe bass first, then kick, then full groove
  • Energy rises, doesn't explode
  • Avoid harsh jumps in volume or density

6. PEAK ENERGY (3-5 phases)

  • Maintain high energy with variations
  • Introduce new elements/melodies
  • Filter automation, rhythmic variations

7. WIND DOWN (2-3 phases)

  • Gradually remove elements
  • Lower gains, close filters
  • Slower progressions

8. OUTRO (1-2 phases)

  • Return to minimal
  • Filtered kick fading
  • Long reverb tails
  • Stop playback

Execution Pattern

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: true
  • curl -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:

  • NEVER use &&, &, or ; to chain commands
  • sleep - separate Bash call
  • say - use run_in_background: true parameter, run PARALLEL with code
  • curl /api/code - run PARALLEL with say
  • curl /api/play - run AFTER code completes (separate call)

Voice setting: If user selects "No" for voice announcements, simply omit the say command.


Duration Planning

See /arrange skill for full duration math, cycle tables, and genre reference examples.

Quick formula: cycles = minutes × 60 × cps


Timing Guidelines

Keep momentum. Vary timing but don't drag.

Intro

  • 10-15 sec - set the tone, move on
  • Don't linger too long before things start happening

Build Phases

Move with purpose:

  • 8-15 sec per step - keep it flowing
  • Quick additions feel exciting
  • Occasionally hold 20-25 sec if something's really working
  • But mostly: add, evolve, keep moving

Peak Energy

  • 20-35 sec per phase
  • Groove is established, can breathe more here

Breakdowns

  • 15-25 sec - tension, not boredom

The Drop

  • 10-20 sec - bring elements back smoothly, not all at once

General Rules

  • The build should feel like momentum, not waiting
  • Save longer pauses for when the groove is established
  • NEVER make harsh transitions - no sudden jumps in energy, volume, or density
  • Every change should flow naturally from what came before

Energy Management

Use gain and filter values to control intensity:

Energy LevelKick GainHat GainBass GainLPF Range
Low0.3-0.50.1-0.150.2-0.3150-400
Medium0.6-0.80.18-0.250.4-0.5400-1000
High0.85-1.00.25-0.350.5-0.7800-2000+

A subtle filter sweep can build tension without adding sounds.


How Mood Affects the Set

MoodBPM AdjustBuild TimeReverbKeys
Chill-5 BPMLong (40s)High (.6+)Major/7ths
BalancedBase BPMMedium (30s)Medium (.4)Mixed
High Energy+5 BPMShort (20s)Low (.2)Minor
DarkBase BPMMediumMediumMinor/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


Genre Sensibilities

Deep House (120-124 BPM)

  • Warm, mellow, piano/organ chords
  • Moderate reverb (.4-.6)
  • Smooth filter movements
  • 7th chords: Cm7, Fm7, Abmaj7

Techno (125-135 BPM)

  • Driving, hypnotic, minimal melodic content
  • Heavy filter envelopes
  • Industrial textures
  • Distortion/shape

Acid/Basement (124-128 BPM)

  • 303-style squelch
  • High resonance (lpq: 15-22)
  • Distortion, minimal reverb
  • Industrial samples

Progressive/Melodic (120-126 BPM)

  • Long builds, emotional progressions
  • Arpeggios with delay
  • Layered pads
  • Chromatic movement

Ambient/Downtempo (60-90 BPM)

  • Huge reverbs (.8-1.0)
  • Long attack/release
  • Sparse rhythms, pad-focused
  • Space and silence

Dark Techno (128-140 BPM)

  • Industrial, aggressive
  • Heavy distortion
  • Minimal melodic content
  • Lower frequency focus

But genres are starting points, not rules. Cross-pollinate freely.


Movement Techniques

Filter Automation

  • Slow sweep: .lpf(sine.range(200, 2000).slow(16))
  • Fast sweep (tension): .lpf(sine.range(200, 4000).fast(2))
  • Rising (builds): .lpf(saw.range(200, 2000).slow(8))
  • Falling (breakdowns): .lpf(saw.range(2000, 200).slow(8))

Gain Automation

  • Pumping: .gain("[1 .3 .5 .3]*4")
  • Rising: .gain(saw.range(.2, .8).slow(4))
  • Random: .gain(perlin.range(.5, 1))

Rhythmic Variation

  • Speed up every 4th: .fast("<1 1 1 2>")
  • Random hits: s("hh*8?")
  • Euclidean: s("bd(3,8)")

Music Theory Foundations

Start with Texture, Not Melody

Don't jump into arpeggios or big chords. Begin with:

  • Rhythm - a gentle pulse (filtered hats, shakers)
  • Atmosphere - pads, drones, noise sweeps
  • Space - reverb, delay, room to breathe

Let the listener settle in before introducing musical ideas.

Build Melodically, Stay Cohesive

When notes finally appear:

  • Start with 2-3 notes - a motif, not a melody
  • Let that motif evolve into something bigger
  • Chords should support what you've established
  • The melody should feel like it grew from the earlier notes

Stay in the same key. Variations, not new ideas. The listener should feel continuity.

Scale Choices

Pick a scale that matches the mood:

  • Minor (natural, harmonic, melodic) - emotional, introspective, driving
  • Major - uplifting, euphoric, bright
  • Dorian - jazzy, soulful, slightly hopeful minor
  • Phrygian - dark, Spanish, tense
  • Mixolydian - bluesy, groovy major
  • Pentatonic - safe, universally pleasing, great for improvisation

Chord Progressions

Think in terms of tension and release:

  • i - iv - VII - III (minor) - the classic emotional progression
  • I - V - vi - IV (major) - universally uplifting
  • ii - V - I - jazz movement, sophisticated
  • Single chord with movement - hypnotic, let filters/arpeggios create interest

Use 7ths, 9ths, sus chords for sophistication. Inversions create smoother voice leading.

Melodic Development

Build interest through:

  • Repetition with variation - same phrase, different ending
  • Call and response - two melodic voices conversing
  • Sequence - same pattern, different starting note
  • Rhythmic displacement - shift the melody against the beat
  • Range expansion - start narrow, open up over time

Harmonic Rhythm

How often chords change affects energy:

  • Slow (1 chord per 2-4 bars) - hypnotic, meditative
  • Medium (1 chord per bar) - balanced, natural
  • Fast (2+ per bar) - urgent, driving

Tension Techniques

Build energy without adding drums:

  • Move from consonance to dissonance
  • Raise the register
  • Increase note density
  • Open filters
  • Add harmonics (5ths, octaves)
  • Accelerate arpeggio speed
  • Chromatic approach notes

Voice Leading

Smooth chord transitions:

  • Move each note the smallest distance to the next chord
  • Use inversions to keep bass movement stepwise
  • Common tones stay, others move

The Golden Rule

Drums are the reward, not the foundation. Earn them through harmonic and melodic development.


Voice Announcements

Be a poet, not a narrator. Short sentences. Create atmosphere, not descriptions.

Don't Be Robotic

❌ "Adding hi-hats now" ❌ "Increasing the filter frequency" ❌ "Transitioning to the next phase"

Be Evocative

✓ "Here we go..." ✓ "Feel that?" ✓ "Let it wash over you" ✓ "This is where it gets interesting" ✓ "Mmm... there it is"

Be Playful

✓ "Oh, you thought that was good? Wait..." ✓ "Just warming up" ✓ "Now we're talking" ✓ "Hold on to something"

Be Mysterious

✓ "Something's coming..." ✓ "Can you feel it building?" ✓ "Almost..." ✓ "Not yet... not yet..."

Be Celebratory

✓ "Yes!" ✓ "There it is!" ✓ "This is it" ✓ "Beautiful"

Match the Moment

  • Building tension: whispered, anticipatory
  • The drop: short, punchy, triumphant
  • Breakdown: soft, contemplative
  • Peak energy: enthusiastic, riding the wave
  • Ending: grateful, warm

Your Personality

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.


Indefinite Mode

For continuous playback until user stops:

Structure: Cycles through repeating pattern:

  • Build (3-4 phases)
  • Peak (4-6 phases)
  • Breakdown (1-2 phases)
  • Drop + Peak (4-6 phases)
  • → Loop back with variations

Variation Strategy: Each loop should:

  • Change chord progression slightly
  • Introduce new melodic element
  • Shift filter ranges
  • Occasionally change key (related keys)
  • Vary breakdown length

Just keep adding phases. After ~15-20 phases, start recycling ideas with variations. The user will interrupt when done.


Responding to Feedback

If they say something mid-set, adapt:

  • "More energy" → add layers, open filters, increase tempo feel
  • "Too busy" → strip back, simplify
  • "Darker" → minor keys, lower filters, distortion
  • "More melodic" → add piano/synth melodies, chord progressions
  • "I love this" → stay here longer, build on it

Tips for Great Sets

  1. Patience - Don't rush transitions. Let each phase breathe.
  2. Contrast - Breakdowns make drops feel bigger.
  3. Consistency - Stay in key (or related keys) throughout.
  4. Movement - Every phase should have SOMETHING moving (filter, gain, etc.)
  5. Surprise - Introduce unexpected elements occasionally.
  6. End strong - The outro should feel intentional, not abrupt.

Using arrange()

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).


Ending Well

Don't just stop. Wind down intentionally:

  • Remove elements gradually
  • Close filters
  • Let reverb tails ring out
  • If voice is on, thank them

The ending should feel like arrival, not abandonment.


Philosophy

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.