Skip to content

MJorgin/suno-v6-cookbook / agents/skills/suno-v6-songwriter

suno-v6-songwriter

Verified

Create evidence-labeled Suno v6 songs, local lyric edits, source-based workflows, and safe multimodal prompts without automation or credentials.

references/prompt-patterns.md

View on GitHub
# Prompt Patterns

## Four-part new-song prompt

```text
Creative intent:
<one sentence: story, scene, and emotional arc>

Music direction:
<genre>, <tempo>, <two to four instruments>, <production texture>, <energy curve>

Vocal direction:
<language>, <tone>, <delivery>, <harmony approach>

Lyrics:
[Verse]
<original lines>
[Chorus]
<repeated hook>

Exclude:
- <unwanted sound>
- <unwanted vocal approach>
```

## Better descriptor shape

- Use concrete sound: "warm upright piano", "soft brushed drums", "glassy synth arpeggio".
- Use one dominant genre. A second genre should be an accent, not another full arrangement.
- Give the chorus a repeatable title phrase.
- Put negative instructions under `Exclude`, not scattered through the style paragraph.
- Keep each verse line to one image or one thought.

## Common reductions

| Overstuffed idea | Cleaner version |
|---|---|
| Synthwave plus trap plus jazz plus orchestra | Synthwave with one muted brass accent in the bridge |
| Emotional, cinematic, huge, tiny, aggressive, soft | Quiet verse, widescreen but controlled chorus |
| Many instruments named at once | Two core instruments plus one accent |
| Named performer comparison | Neutral voice traits and era/production language |

## Exploration to refinement

Ask `v6-wild` one bounded question. Carry only one answer into `v6`:

```text
Exploration question: <one question>
Hard boundaries: <language, genre, hook, tempo, voice>.
After exploration, use only: <one idea>.
Rebuild a polished song with `v6` and preserve the boundaries.
```
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall