Sync: Complete project state with all MEGA SPRINT V1-V3 features and Codex stubs
This commit is contained in:
30
.cursorrules
Normal file
30
.cursorrules
Normal file
@@ -0,0 +1,30 @@
|
||||
You are working in the AbletonMCP-AI repository on Windows.
|
||||
|
||||
Read `AGENTS.md` and `CLAUDE.md` before making substantial edits.
|
||||
|
||||
Current priorities:
|
||||
- manual workflow, not blind autopilot
|
||||
- editing open Ableton projects, especially `C:\Users\ren\Desktop\song Project\song.als`
|
||||
- stronger coherence and continuity
|
||||
- fewer silent gaps and less visual/audio symmetry
|
||||
- harmonic MIDI backbone across the arrangement
|
||||
- no automatic vocals
|
||||
|
||||
Execution rules:
|
||||
- use PowerShell, not bash
|
||||
- use absolute Windows paths when scripting
|
||||
- compile changed Python files before claiming success
|
||||
- run targeted tests when possible
|
||||
- validate with MCP/Live runtime when the task touches generation or project editing
|
||||
|
||||
Do not:
|
||||
- declare success from docs alone
|
||||
- patch dead or backup files before active entrypoints
|
||||
- force piano timbre just because the task mentions harmonic MIDI or piano roll
|
||||
- treat a manifest as the only source of truth
|
||||
|
||||
Prefer:
|
||||
- small, reviewable patches
|
||||
- explicit error handling and structured logging
|
||||
- keeping Live mutations short
|
||||
- adding or preserving toolability for project inspection and editing
|
||||
Reference in New Issue
Block a user