2. Philosophy
← Introduction · Guide contents · Next: Thinking in semantic roles →
Treat the workflow as part of the composition
Section titled “Treat the workflow as part of the composition”The creative object is larger than the text entered into a prompt box. It includes the source material, the order of operations, the role assigned to each generation, the controls used at each stage and the listening decision that determines what happens next.
That makes workflow design part of the musical thinking rather than an administrative step around it. A melodic Anchor, a Kinetic Engine, a Mashup used for assembly and a Cover used for cohesion can each contribute something different to the same composition.
Preserve ideas, not labels
Section titled “Preserve ideas, not labels”When I make a Cover, I am rarely trying to preserve an entire genre. I am trying to preserve the thing that makes the song itself worth carrying forward: a bass line, a vocal cadence, a melodic contour, a harmonic movement, a particular kind of rhythmic drive.
That changes the opening question.
Instead of:
How do I turn this into Liquid Drum and Bass?
I ask:
What musical idea must survive when this becomes Liquid Drum and Bass?
The destination genre still matters, but it is no longer doing every job in the prompt.
Give every instruction a responsibility
Section titled “Give every instruction a responsibility”I do not judge a prompt by how dense it looks. A short prompt can be precise; a long prompt can be a pile of unresolved suggestions.
The useful question is whether every instruction has a reason to be there.
Successful prompt ≠ more wordsSuccessful prompt = clearer responsibilitiesIf the rhythm drifts, refine the rhythmic behaviour. If the vocal sounds synthetic, describe the delivery. If the arrangement stalls, address motion or structure. Adding three unrelated textures may make the prompt longer without touching the problem.
Listen before refining
Section titled “Listen before refining”The first result often reveals the real problem. I may begin knowing the destination but not yet know which behaviours will need protection. Once I can hear the failure—halftime drift, static arrangement, over-processed vocals, a disappearing melodic identity—the next prompt becomes much easier to write.
This is why I treat prompting as an iterative design process rather than a one-shot incantation.
← Introduction · Guide contents · Next: Thinking in semantic roles →
