livepilot 1.10.7 → 1.10.8

package/livepilot/skills/livepilot-composition-engine/references/transition-archetypes.md

@@ -1,102 +0,0 @@
-# Transition Archetypes Reference
-
-Common transition patterns returned by `plan_transition` and usable with `apply_gesture_template`.
-
-## Energy-Up Transitions
-
-### riser_sweep
-A filter or noise sweep that builds energy into the next section.
-
-- Duration: 2-8 bars
-- Implementation: ascending automation on filter cutoff (20% to 100%) plus optional white noise riser
-- Best for: verse-to-chorus, breakdown-to-drop
-- Tools: `set_clip_automation`, `apply_automation_shape(track_index, clip_index, parameter_type="device", curve_type="exponential", start=0, end=1)`
-
-### drum_build
-Progressive addition of percussion layers leading to the downbeat.
-
-- Duration: 2-4 bars
-- Implementation: add hi-hat rolls (increasing density), snare fills, kick pattern intensification
-- Best for: pre-chorus builds, intro-to-verse
-- Tools: `add_notes` for fill patterns, `set_track_volume` automation for gradual volume increase
-
-### harmonic_tension
-Build tension through suspended or unresolved harmony before resolving at the section boundary.
-
-- Duration: 1-4 bars
-- Implementation: sus4 or dominant 7th chord sustained over the transition, resolving on beat 1 of the new section
-- Best for: verse-to-chorus, bridge-to-final-chorus
-- Tools: `modify_notes` to alter chord voicings, `add_notes` for tension tones
-
-### stacking
-Gradually add instrumental layers, one per bar or phrase, building density.
-
-- Duration: 4-16 bars
-- Implementation: unmute tracks in sequence (percussion first, then bass, then harmony, then leads)
-- Best for: intro builds, post-breakdown rebuilds
-- Tools: `set_clip_automation` on track volume, `set_track_mute` for discrete layer adds
-
-## Energy-Down Transitions
-
-### strip_down
-Remove elements one by one to reduce energy before a quieter section.
-
-- Duration: 2-8 bars
-- Implementation: mute layers in reverse order of importance (effects first, then leads, then harmony, keeping bass and kick last)
-- Best for: chorus-to-verse, pre-breakdown
-- Tools: `set_track_mute`, `set_track_volume` automation with gradual decrease
-
-### filter_close
-Low-pass filter sweep closing down to muffle the sound.
-
-- Duration: 2-4 bars
-- Implementation: descending automation on master or bus filter cutoff (100% to 20-30%)
-- Best for: section endings, transitions to breakdowns
-- Tools: `set_clip_automation`, `apply_automation_shape(track_index, clip_index, parameter_type="device", curve_type="exponential", start=1, end=0)`
-
-### reverb_wash
-Increase reverb wet level to blur the previous section into the next.
-
-- Duration: 1-2 bars
-- Implementation: automate send level to reverb return (0% to 60-80%), then cut dry signal on beat 1
-- Best for: hard section changes where you want continuity of space
-- Tools: `set_track_send` automation, `set_clip_automation`
-
-## Neutral Transitions
-
-### hard_cut
-Instant transition with no preparation. The contrast itself creates impact.
-
-- Duration: 0 bars (instantaneous)
-- Implementation: no transition processing — the sections simply abut
-- Best for: drop entries after silence, genre-specific style (punk, some electronic)
-- Constraint: works best when the energy delta is extreme (silence to loud, or vice versa)
-
-### crossfade
-Gradual overlap of outgoing and incoming sections.
-
-- Duration: 1-4 bars
-- Implementation: outgoing section fades out while incoming fades in, overlapping by the crossfade duration
-- Best for: ambient, cinematic, smooth genre transitions
-- Tools: `set_clip_automation` on track volumes with opposing curves
-
-### fill_break
-A drum fill followed by a brief silence (1-2 beats) before the new section.
-
-- Duration: 1 bar
-- Implementation: drum fill on the last bar, then all instruments drop for 1-2 beats, new section enters on beat 3 or 4
-- Best for: rock, pop, funk section transitions
-- Tools: `add_notes` for the fill, `set_track_mute` or volume automation for the gap
-
-## Choosing the Right Archetype
-
-| From -> To | Recommended | Alternative |
-|------------|-------------|-------------|
-| Intro -> Verse | stacking | drum_build |
-| Verse -> Chorus | riser_sweep, drum_build | harmonic_tension |
-| Chorus -> Verse | strip_down | filter_close |
-| Verse -> Bridge | harmonic_tension | strip_down |
-| Bridge -> Final Chorus | riser_sweep + drum_build | harmonic_tension |
-| Chorus -> Breakdown | strip_down, hard_cut | filter_close |
-| Breakdown -> Drop | riser_sweep | drum_build + stacking |
-| Any -> Outro | strip_down, reverb_wash | filter_close |

package/livepilot/skills/livepilot-core/SKILL.md

@@ -1,184 +0,0 @@
----
-name: livepilot-core
-description: Core discipline for LivePilot — agentic production system for Ableton Live 12. 323 tools across 45 domains. This skill should be used whenever working with Ableton Live through MCP tools. Provides golden rules, tool speed tiers, error handling protocol, and pointers to domain and engine skills.
----
-
-# LivePilot Core — Ableton Live 12
-
-Agentic production system for Ableton Live 12. 323 tools across 45 domains, three layers:
-
-- **Device Atlas** — 1305 devices indexed (81 enriched with sonic intelligence, 683 drum kits). Consult `atlas_search` or `atlas_suggest` before loading any device. Never guess a device name.
-- **M4L Analyzer** — Real-time audio analysis on the master bus (8-band spectrum, RMS/peak, key detection). Optional — all core tools work without it.
-- **Technique Memory** — Persistent storage for production decisions. Consult `memory_recall` before creative tasks to understand user taste.
-
-## Golden Rules
-
-1. **Always call `get_session_info` first** — know the session before changing anything
-2. **Verify after every write** — re-read state to confirm changes took effect
-3. **Use `undo` liberally** — mention it to users when doing destructive ops
-4. **One operation at a time** — verify between steps
-5. **Track indices are 0-based** — negative for return tracks (-1=A, -2=B), -1000 for master
-6. **NEVER invent device/preset names** — always `search_browser` first, use exact `uri` from results. Exception: `find_and_load_device` for built-in effects only ("Reverb", "Delay", "Compressor", "EQ Eight", "Saturator", "Utility")
-7. **Color indices 0-69** — Ableton's fixed palette
-8. **Volume 0.0-1.0, pan -1.0 to 1.0** — normalized, not dB
-9. **Tempo range 20-999 BPM**
-10. **Always name tracks and clips** — organization is part of the process
-11. **Respect tool speed tiers** — see below
-12. **ALWAYS report tool errors** — never silently swallow errors. Include: tool name, error message, fallback plan
-13. **Verify plugin health after loading** — check `health_flags`, `mcp_sound_design_ready`, `plugin_host_status`. If `parameter_count` <= 1 on AU/VST → dead plugin, delete and replace
-14. **Use `C hijaz` for Hijaz/Phrygian Dominant keys** — avoids false out-of-key warnings
-15. **VERIFY AFTER EVERY WRITE** — mandatory, non-negotiable:
-    - After `set_device_parameter` or `batch_set_parameters`: read `value_string` in the response to confirm the actual Hz/dB/% value makes sense
-    - After any filter, EQ, or effect parameter change: call `get_track_meters(include_stereo=true)` and verify the target track has non-zero left AND right levels
-    - After `apply_automation_recipe`: check that the recipe didn't push the parameter to an extreme that kills audio
-    - If a track's stereo output drops to 0: the effect is killing the signal — check `get_device_parameters` for `value_string`, fix, re-verify
-    - **Parameter ranges are NOT always 0-1.** Auto Filter Frequency is 20-135. Bit Depth is 1-16. Always read `value_string` to see actual units.
-16. **NEVER apply automation recipes without understanding the target parameter's range** — recipes generate 0-1 curves that get auto-scaled for device parameters, but always verify the result
-17. **LivePilot_Analyzer must be LAST on master chain** — always place after ALL effects (EQ, Compressor, Utility, etc.) so it measures the final post-processing output, not the raw signal. When loading effects on master, either load them before the analyzer or move the analyzer to end afterward
-
-## Tool Speed Tiers
-
-### Instant (<1s) — Use freely
-All 323 tools plus M4L perception tools.
-
-### Fast (1-5s) — Use freely
-`analyze_loudness` · `analyze_mix` · `analyze_sound_design`
-
-### Slow (5-15s) — Tell the user first
-`compare_to_reference` · `analyze_spectrum_offline` · `read_audio_metadata`
-
-**Escalation pattern:** Start fast, escalate only with consent:
-```
-Level 1 (instant):  get_master_spectrum + get_track_meters
-Level 2 (fast):     analyze_loudness + analyze_mix
-Level 3 (slow):     compare_to_reference + analyze_spectrum_offline
-```
-
-## Error Handling Protocol
-
-Report ALL errors to the user immediately. Common failure modes:
-- **Dead AU/VST plugin** — `parameter_count` <= 1 → delete, replace with native
-- **Sample-dependent plugin** — granular synths produce silence without samples → use self-contained synths (Wavetable, Operator, Drift, Analog)
-- **Empty Drum Rack** — bare rack = silence → always load a kit preset
-- **M4L bridge timeout** — device may be busy or removed → retry or skip analyzer features
-- **Connection timeout** — Ableton unresponsive → check if session is heavy
-- **Volume reset on scene fire** — Ableton restores mixer state when firing scenes. Always re-apply `set_track_volume`/`set_track_pan` after `fire_scene` if your mix settings differ from what was stored in the clips
-- **M4L Analyzer not connected** — if `get_master_spectrum` errors with "Analyzer not detected", auto-load it: `find_and_load_device(track_index=-1000, device_name="LivePilot_Analyzer")`. If it errors with "UDP bridge not connected", try `reconnect_bridge` first
-- **Another client connected** — Remote Script only accepts one TCP client on port 9878. If you see this error, the MCP server is already connected. Use MCP tools instead of raw TCP
-
-## Technique Memory
-
-Three modes:
-- **Informed (default):** `memory_recall` before creative tasks, let past decisions influence new ones
-- **Fresh:** Skip memory when user wants something new ("ignore my history", "surprise me")
-- **Explicit recall:** `memory_recall` → `memory_get` → `memory_replay` when user references a saved technique
-
-## Wonder Mode — Stuck-Rescue Routing
-
-- Use Wonder (`enter_wonder_mode`) for creative ambiguity and session rescue
-- Do not fabricate three variants when only one real option exists
-- Do not describe a branch as previewable unless it has a valid `compiled_plan`
-- Prefer Wonder when `detect_stuckness` confidence > 0.5
-- Prefer Wonder when the user's request is emotionally-shaped, not parametric
-- Load `livepilot-wonder` skill for full workflow guidance
-
-## Creative Sound Design Knowledge
-
-Before setting device parameters, consult the knowledge corpus for informed creative choices. Read the relevant file BEFORE making changes:
-
-| User says | Read this file |
-|-----------|---------------|
-| "make it breathe" / "organic" / "alive" / "warm" / "cold" / "anxious" / "nostalgic" | `references/device-knowledge/creative-thinking.md` — emotional-to-technical mapping, physical world modeling |
-| "what effect chain for [genre]" / "dub techno" / "trap" / "SOPHIE" / "Arca" / "ambient" | `references/device-knowledge/chains-genre.md` — complete chains per genre |
-| "how to use Wavetable/Drift/Analog/Operator/Meld" | `references/device-knowledge/instruments-synths.md` — parameter-level recipes |
-| "distortion" / "saturation" / "Roar" / "Saturator" / "Redux" | `references/device-knowledge/effects-distortion.md` — every curve type, creative applications |
-| "reverb" / "delay" / "echo" / "space" / "dub" | `references/device-knowledge/effects-space.md` — dub recipes, shimmer chains |
-| "spectral" / "Resonators" / "Corpus" / "Vocoder" / "weird" / "experimental" | `references/device-knowledge/effects-spectral.md` — drum-to-melody, cross-synthesis |
-| "automate" / "evolve" / "arc" / "movement" / "filter sweep" | `references/device-knowledge/automation-as-music.md` — shapes, macro gestures, density mapping |
-| "sound design" / "make it interesting" / "more complex" | `references/sound-design-deep.md` — master techniques from Villalobos, SOPHIE, Basic Channel |
-
-**Rule:** Never set effect parameters from memory alone when the corpus has specific guidance. Read the file first, then apply the technique.
-
-## Domain Skills
-
-For domain-specific workflows, load the appropriate skill:
-
-| Skill | When to use |
-|-------|-------------|
-| `livepilot-devices` | Loading, browsing, configuring devices and presets |
-| `livepilot-notes` | Writing notes, theory, generative algorithms, MIDI I/O |
-| `livepilot-mixing` | Volume, pan, sends, routing, automation |
-| `livepilot-arrangement` | Song structure, scenes, arrangement view |
-
-## V2 Engine Skills
-
-For agentic evaluation loops, load the appropriate engine skill:
-
-| Skill | When to use |
-|-------|-------------|
-| `livepilot-mix-engine` | Critic-driven mix analysis and iterative improvement |
-| `livepilot-sound-design-engine` | Critic-driven patch analysis and refinement |
-| `livepilot-composition-engine` | Section analysis, transitions, motifs, form |
-| `livepilot-performance-engine` | Live performance with safety constraints |
-| `livepilot-evaluation` | Universal before/after evaluation loop |
-
-## Reference Corpus
-
-Deep production knowledge in `references/`:
-
-| File | Content |
-|------|---------|
-| `references/overview.md` | All 323 tools with params and ranges |
-| `references/device-atlas/` | 280+ device corpus with URIs and presets |
-| `references/midi-recipes.md` | Drum patterns, chord voicings, humanization |
-| `references/sound-design.md` | Synth recipes, device chain patterns |
-| `references/mixing-patterns.md` | Gain staging, compression, EQ, stereo |
-| `references/automation-atlas.md` | 16 curve types, 15 recipes, spectral mapping |
-| `references/ableton-workflow-patterns.md` | Session/arrangement workflows |
-| `references/memory-guide.md` | Technique memory usage and quality templates |
-| `references/m4l-devices.md` | M4L bridge command reference |
-
-## V2 Orchestration Layer
-
-For complex requests, use the V2 orchestration flow instead of ad-hoc tool calls:
-
-### Standard V2 Flow
-1. **`route_request`** — classify the request, get recommended engines and workflow mode
-2. **`get_session_kernel`** — build the unified turn snapshot (session, capabilities, taste, memory)
-3. **`propose_next_best_move`** — get ranked semantic move suggestions (taste-aware)
-4. **`preview_semantic_move`** — see what a move will do before committing
-5. **`apply_semantic_move`** — compile and execute the move (mode-dependent)
-6. **Evaluate** — use the appropriate evaluator to check the result
-
-### Semantic Moves
-High-level musical intents that compile to deterministic tool sequences. 5 families:
-- **mix** — `tighten_low_end`, `widen_stereo`, `make_punchier`, `darken_without_losing_width`, `reduce_repetition_fatigue`, `make_kick_bass_lock`, `reduce_foreground_competition`
-- **arrangement** — `create_buildup_tension`, `smooth_scene_handoff`, `increase_contrast_before_payoff`, `refresh_repeated_section`
-- **transition** — `increase_forward_motion`, `open_chorus`, `create_breakdown`, `bridge_sections`
-- **sound_design** — `add_warmth`, `add_texture`, `shape_transients`, `add_space`
-- **performance** — `recover_energy`, `decompress_tension`, `safe_spotlight`, `emergency_simplify`
-
-Use `list_semantic_moves(domain="mix")` to discover available moves.
-
-### Experiment Branching
-For creative exploration, use experiment branching to compare multiple approaches:
-1. `create_experiment(request_text="make it punchier")` — auto-proposes branches
-2. `run_experiment(experiment_id)` — trials each branch (apply → capture → undo)
-3. `compare_experiments(experiment_id)` — rank branches by score
-4. `commit_experiment(experiment_id, branch_id)` — apply winner permanently
-
-### Taste-Aware Ranking
-The system learns user preferences from kept/undone moves:
-- `get_taste_graph()` — current taste model
-- `explain_taste_inference()` — human-readable explanation
-- `rank_moves_by_taste(move_specs)` — sort options by preference fit
-- `propose_next_best_move` automatically applies taste ranking when evidence exists
-
-### Musical Intelligence
-Song-level analysis beyond parameters:
-- `detect_repetition_fatigue()` — clip overuse, section staleness
-- `detect_role_conflicts()` — tracks fighting for the same space
-- `infer_section_purposes()` — label sections as setup/tension/payoff/contrast/release
-- `score_emotional_arc()` — does the song have a satisfying build→climax→resolve?
-- `analyze_phrase_arc()` — capture and evaluate musical phrases
-- `compare_phrase_renders()` — compare phrase variants side by side