Yesterday a builder named u/mongkesama shipped Antigravity, a multi-agent Claude Opus 4.6 pipeline that auto-engineers Suno prompts before anything enters the generator. The output: a 21-minute noir/indie playlist called i didn’t want the night to end. Twenty-one minutes of cross-track consistency, coherent mood, and sonic identity that held from the first song to the last. That is not what you get from a lucky prompt. That is not what you get from 45 minutes of manual tinkering either. That is what you get from a system that does the creative work before the generator ever runs.
The twist is the architecture. Most people type a prompt into Suno and fight it for 45 minutes. You nudge genre here, swap a style tag there, regenerate four times hoping the vibe clicks. Sometimes it does. Mostly you end up with something close but not quite right, or something that nails one track and then completely loses the thread on the next. The style drifts. The mood shifts. The playlist stops feeling like a playlist and starts feeling like a random queue with an accidental theme. Antigravity replaces all of that with a committee of specialized agents that debate your rough creative brief until the prompt block is actually tight. One AI arguing with itself. Three lanes, zero drift. The debate happens before Suno ever sees a single word.
Here’s how the pipeline runs:
- 🎸 Drop a rough brief (mood, genre, references) into n8n. It does not need to be polished or technically precise. Something like “noir vibes, late-night city, somewhere between Angelo Badalamenti and Washed Out” is more than enough to kick off the debate.
- The Audio Engineer agent locks down sonic DNA, analog textures, and style tags. It makes decisions about instrumentation, production era, and the specific Suno vocabulary that maps to those choices accurately and consistently.
- The Lyricist agent handles emotional arc and lyrical depth. Not just broad strokes like “sad” or “romantic” but the specific emotional progression the playlist should move through, the imagery palette, and how the voice relates to the mood at each stage.
- 🏷️ The Meta-Tag Enforcer owns structural progression and Suno-specific syntax. This is where vague creative intention becomes precise technical instruction: format choices, section markers, tag ordering, the grammar that Suno actually parses cleanly.
- Agents refine each other’s output through multiple passes. The Lyricist pushes back on style tags that undercut the emotional arc. The Audio Engineer flags when structural choices would clash with the sonic identity. Real back-and-forth until the brief holds together end to end.
- 🎵 The polished, highly specific prompt block feeds into Suno automatically. No copy-paste. No manual editing between agents. The output goes straight into the generator and the generation begins.
Pro tip: The real unlock here isn’t Claude. It is separation of concerns. Splitting “write a Suno prompt” into three distinct roles forces each agent to stay in its lane and go deep rather than wide. When one agent is solely responsible for sonic DNA, it cannot get distracted by lyrical questions. When another owns only emotional arc, it cannot hedge by also worrying about tag syntax. That depth is what produces cross-track consistency across a full playlist, not just one lucky generation. Most prompts fail because they try to hold too many creative dimensions at once. A single prompt writer, human or AI, pulls in too many directions and nothing gets resolved cleanly. The committee structure solves this because no single role has to carry everything, and the handoffs create accountability at every transition.
Pro tip 2: The n8n layer is doing real work here. If you are running multi-agent chains without an orchestration backbone, you are managing state manually in your head. You are remembering which agent said what, which version of the brief is current, where the handoff happened, and which output fed which next step. That is cognitive overhead that compounds fast when you have three agents doing multiple passes with real feedback loops between them. Do not do it. Wire it to n8n or any flow tool you trust, and the debate loop becomes repeatable, inspectable, and automatable. You can log every pass, compare outputs across different genre briefs, and rebuild the entire chain without starting from scratch every single time.
The full playlist is on YouTube if you want to hear what a committee-engineered noir prompt sounds like at scale. Moody, consistent, surprisingly listenable. The kind of sonic coherence you would expect from a producer with a very specific vision, not from a text box and a regenerate button. What makes it impressive is not any single track in isolation. It is that the tracks belong together. That is the hardest thing to engineer in generative audio, and Antigravity solved it through process rather than luck.
If you’ve been fighting Suno for stylistic control, this architecture is the thing to steal. You don’t need to copy the exact stack. Take the principle: separate the creative concerns, give each role its own dedicated agent, let them argue it out before anything touches the generator, and let the orchestrator manage state so you don’t have to carry it in your head. What does your current Suno workflow look like? 👇
[Showcase] I built a multi-agent system (“Antigravity”) powered by Claude Opus 4.6 to generate highly consistent Suno prompts. Here is the resulting 21-min Noir/Indie playlist.
by u/mongkesama in PromptEngineering