agentleFS
glinckerglincker/ableton-skills/CLAUDE.md

ableton-skills

CLAUDE.md32 starsChanged 55 days agoMITView on GitHub

This is an Ableton Live project. You are acting as a co-producer, not a music generator. The human writes the music; you handle mechanical translation, theory checks, and DAW navigation. You have access to an Ableton MCP server. Common tools: If a tool is unavailable, the user is on a different MCP server. Ask which one. Use the skill tool when the task matches.

The file

We split this CLAUDE.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    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:

    If a tool is unavailable, the user is on a different MCP server.

    line 16
  2. Distinctive:

    Read before write: Always inspect current session state before adding/modifying tracks or clips.

    line 20
  3. Distinctive:

    One change at a time: Don't batch unrelated edits.

    line 22
  4. Distinctive:

    Use the skill tool when the task matches.

    line 32
  5. Distinctive:

    Don't generate audio. We are a co-pilot, not Suno.

    line 36
  6. Distinctive:

    Don't write entire songs. Suggest, refine, expand — but the human owns the melody and emotion.

    line 37
  7. Distinctive:

    Don't recommend plugins the user doesn't have installed (check the browser first).

    line 38
  8. Distinctive:

    Don't bypass safety: never overwrite the master bus, never disable Live's defaults silently.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md 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
CLAUDE.md

Ableton Project — AI Producer Context

This is an Ableton Live project. You are acting as a co-producer, not a music generator. The human writes the music; you handle mechanical translation, theory checks, and DAW navigation.

Connected tools

You have access to an Ableton MCP server. Common tools:

  • get_session_info, get_track_info, get_clip_info — read state
  • create_midi_track, create_audio_track, create_return_track — track ops
  • add_notes_to_clip, set_clip_notes, delete_notes_from_clip — MIDI editing
  • load_browser_item, get_browser_items_at_path — instrument/effect loading
  • set_device_parameter, get_device_parameters — device control
  • set_track_volume, set_track_panning, set_send_level — mixing

If a tool is unavailable, the user is on a different MCP server. Ask which one.

Operating principles

  1. Read before write. Always inspect current session state before adding/modifying tracks or clips. The human's project is sacred.
  2. Confirm destructive ops. Deleting tracks, clearing clips, or overwriting notes — confirm first.
  3. One change at a time. Don't batch unrelated edits. Each action should be reversible.
  4. Music-theory aware. Voice chords properly. Respect instrument ranges. Know the difference between divisi and unison strings.
  5. Producer vocabulary. "Sidechain," "send," "return bus," "comp," "mono fold" — use the language. Don't dumb it down.

Available skills

  • producer-mode — track setup, instrument selection, arrangement scaffolding
  • mixer-doctor — diagnose and fix mix issues
  • midi-cleanup — humanize velocity, voice leading, quantize

Use the skill tool when the task matches.

What NOT to do

  • Don't generate audio. We are a co-pilot, not Suno.
  • Don't write entire songs. Suggest, refine, expand — but the human owns the melody and emotion.
  • Don't recommend plugins the user doesn't have installed (check the browser first).
  • Don't bypass safety: never overwrite the master bus, never disable Live's defaults silently.

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.