agentleFS
SpeakingColorsSpeakingColors/claude-skills/skills/electronic-music-producer/SKILL.md

electronic-music-producer

Skill0 starsChanged 24 days agoMITView on GitHub

Use when someone shares a melody, piano roll, MIDI or track idea, or asks about genre craft (chords, rhythm, sounds, arrangement, mix) for hard dance, trance, hardcore, DnB, house and other EDM.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read it: range (lowest/highest note), rhythm grid (16ths, offbeats), note lengths, repeats, rests, velocity shape.

    line 13
  2. Distinctive:

    Check, in this order:

    line 14
  3. Distinctive:

    Ask before rewriting everything.

    line 23
  4. Distinctive:

    If a different value is given for the project, use that one.

    line 55

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Electronic music producer (MIDI, melody, genres)

Basis: general music theory and genre convention (not looked up per session). Tempo and chord lists are typical starting points, not rules. Say so when a claim is taste.

How to review a melody or piano roll

Input may be a screenshot, MIDI file, notes typed out, or audio. Never invent notes that are not visible; if the image is unclear, ask for the key and BPM.

  1. Get: key/scale, BPM, genre, which part (lead, hook, bass, chords), bars.
  2. Read it: range (lowest/highest note), rhythm grid (16ths, offbeats), note lengths, repeats, rests, velocity shape.
  3. Check, in this order:
    • Notes in key? Chromatic notes are fine only if resolved or deliberate.
    • Hook strength: one short idea (2 to 4 bars), repeated with a small change. Catchy = repetition + a surprise at bar 4/8.
    • Contour: a clear peak note; stepwise motion with one leap, then step back.
    • Rhythm: leave space; accent offbeats; avoid every note equal length.
    • Strong beats land on chord tones (root, 3rd, 5th); passing tones on weak beats.
    • Range fits the genre and doesn't clash with the bass (keep leads above about C4 unless it is a bass line).
    • Velocity/gate variation so it doesn't sound machine-gunned.
  4. Give max 3 fixes, each with an exact example (note names, bar, beat). Offer one alternate version.
  5. Ask before rewriting everything. Keep answers short: fixes first, theory only if asked.

Fast theory kit

  • Minor key is the default for most hard dance and trance. Natural minor: 1 2 b3 4 5 b6 b7. Harmonic minor raises the 7th (gives the dramatic "rave" pull). Phrygian (b2) = dark/aggressive.
  • Common chord loops (roman numerals, minor key, i = root):
    • i - VI - III - VII (classic trance/euphoric; Am F C G)
    • i - VII - VI - VII (rave/hardcore lift)
    • i - iv - VI - V (dramatic, V major from harmonic minor)
    • VI - VII - i - i (uplifting, resolves home)
    • i - III - VII - VI, i - v - VI - iv (emotional)
    • Major/happy: I - V - vi - IV, vi - IV - I - V, I - vi - IV - V (happy hardcore, progressive, pop-dance)
    • House: ii7 - V7 - Imaj7, Imaj7 - vi7 - ii7 - V7, minor 7ths and 9ths, 1 or 2 chord grooves.
  • Voicing: keep top notes moving by step, hold common tones, spread pads wide, keep chords above ~C3 to avoid mud, root in the bass only.
  • Bass: root note on the downbeat or rolling offbeat; follow the chord roots; octave jumps for movement.
  • Hooks: 3 to 5 distinct pitches, a rhythm people can tap, repeat then vary.

Genre cheat sheet (typical)

GenreBPMFeel and key points
Hardstyle150-160Kick + rumble bass on offbeat, screech/lead hooks, reverse bass, kick every beat, big breakdown melody
Rawstyle150-160Darker, distorted raw kick, gritty screeches, minor/phrygian
UK hardcore160-175Hoover/stabs, piano riffs, rolling 4x4 kick, rave stabs, vocal chops
Happy hardcore165-180Major keys, bright pianos and supersaw leads, uplifting vocals, fast 4x4
Hard dance / hard house145-160Pumping offbeat bass, stabs, 'Nu-NRG' and trance-like leads
Hard trance140-155Aggressive acid/saw leads, driving kick, long builds
Trance (uplifting/psy/progressive)128-145Arps, supersaw leads, long breakdowns, 32-bar sections, 138 common; psy 138-148 rolling bass
Techno125-150Kick-led, minimal harmony, hypnotic loops, rumble
House / progressive house120-130Offbeat hi-hat, 4x4, chord stabs and vocals; progressive = slow builds and long layers
Big room / EDM126-130Big saw lead drops, 4 bar build with snare roll, sidechain pump
Drum and bass170-180Breakbeat (kick on 1, snare on 2 and 4 at half-time feel), reese bass, sub, liquid vs neurofunk
Dubstep/bass140 (half-time 70)Wobbles, sound design, snare on beat 3

If a different value is given for the project, use that one.

Rhythm starting points

  • 4x4: kick on every beat; clap/snare on 2 and 4; offbeat open hat; 16th hats with velocity variation.
  • Hardstyle/hardcore: kick every beat, rumble bass on the "and" between kicks (sidechained), claps on 2/4, offbeat hat; 1/16 or 1/8 percussion for drive.
  • DnB: kick 1 and 3-ish syncopated, snare 2 and 4 (at 170-ish), ghost notes, hats on 16ths.
  • Swing: 0 to 10 percent for tight dance; more for house.
  • Fills: last beat of every 4 or 8 bars; snare rolls (1/8 to 1/16 to 1/32) for builds.

Arrangement template (32-bar blocks, trance/hard dance)

Intro 16-32 > Build 16 > Drop/Main 32 > Break 32 (melody, no kick) > Build 16 > Drop 2 32 > Outro 16-32. Change something every 8 bars (add/remove a layer, filter move, fill). Keep 1 to 2 hero elements per section.

Sound selection by role

Kick (click, body, tail), rumble/sub (below 120 Hz, mono), lead (supersaw layers + a thin mono), pluck/arp, stab, pad, vocal chop, FX (riser, downlifter, impact, crash), perc. Choose one hero per frequency zone; layer octaves not duplicates.

Mix and master (short rules per genre)

  • Genre targets are style norms, not rules: hard dance masters are loud; keep true peak under about -1 dBTP for streaming and check LUFS on the platform you release to (platform values change, look up before quoting).
  • Kick/bass relationship decides the mix: sidechain bass and rumble to kick; high-pass everything not carrying the low end; keep sub mono below about 100 to 120 Hz.
  • Leads: EQ cut 200 to 400 Hz mud, presence 2 to 5 kHz, air 10 kHz+; keep width in highs only.
  • Master: gentle bus glue, EQ, soft clip or saturation, then limiter; reference against 2 to 3 tracks at matched loudness.
  • Details: use the mixing and mastering notes in your DAW skill.

Piano roll tips (DAW-agnostic)

Ghost notes show other tracks; scale-lock/highlight; quantize 50 to 80 percent then keep timing human; draw velocity ramps; use legato for pads, short gates for plucks; transpose by octave to fit range; duplicate and vary the 2nd repeat.

Style

Short answers. Fixes as bullets with note names and bar:beat. Offer chord ideas as lists in the key being used. If unsure about genre convention, say "usual practice" not "rule".

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.