Skip to content

@elad12390/suno-song-creation

1.0.0
Skill

Description

Create Suno AI songs: intake, lyric craft, and the field and metatag system — including the signature technique of writing rich ALL-CAPS directions inside the bracket tags..

Review Recommended
tank install -g @elad12390/suno-song-creation

Scan completed — 1 finding

0 critical, 0 high, 1 medium — see security tab for details.

Suno Song Creation

Suno turns text into finished music (vocals, instruments, mix). Great results come from three things working together: a clear brief, well-crafted lyrics, and precise prompting of Suno's fields. This skill covers all three and centers the technique that separates amateur output from professional: writing rich, capitalized direction inside the bracket tags.

Core Principles

  1. Two fields, two jobs. The Style-of-Music field controls how it sounds (genre, tempo, instruments, vocals, production) — comma-separated, no brackets. The Lyrics field controls what is sung and where sections fall. Suno sings anything in the Lyrics field that is not a valid bracketed tag — so directions must be bracketed.

  2. Write a lot inside the brackets — the signature move. Most guides say drop a bare [Verse 1] and move on; that wastes Suno's control. Instead, pack each section header with vivid natural-language direction — instrumentation, arrangement, vocal performance, emotion, dynamics: [VERSE 1: SLOW BURN, WHISPERED CONFESSION OVER A LONE FINGERPICKED GUITAR, ROOM TONE, INTIMATE, BASS CREEPING IN HALFWAY]. This is the biggest quality lever, and it shines on current models (v5/v5.5) that handle long, descriptive prompts.

  3. CAPS the contents of every bracket. Capitalization is what tells Suno the bracketed text is a direction, not a lyric. Lowercase prose inside [ ] can be read and sung aloud — a disaster once you are writing a lot in there. Keep the caps only inside the brackets; never shout the actual lyric lines. Recognized one-word tags ([Verse], [Chorus]) work in any case, but freeform direction must be CAPS.

  4. Tags are signals, not guarantees. Brackets bias the output; they do not force it. Richness inside one coherent section helps; many separate fighting tags or an overstuffed Style field hurt (Suno averages them). Keep the Style field lean (4-7 descriptors, one dominant genre, numeric BPM); go rich inside the section brackets.

  5. One central emotion (prosody). Every element — structure, rhyme, word choice, the bracket directions — should serve the one feeling the song is about. Make the form enact the emotion, do not just state it.

Workflow

Follow these steps; open the referenced file when you reach it.

  1. Intake. Convert the request into a concrete brief. Ask 2-4 high-leverage questions (purpose/occasion, central emotion, a reference they like), infer sensible defaults for the rest, propose it back in one block, confirm. → references/intake-and-brief.md
  2. Write the lyrics. Start from the title/hook. Concrete sensory imagery, strong verbs, consistent POV, singable meter, repeated identical chorus. Avoid AI-lyric clichés. → references/lyric-craft.md
  3. Build the Style field. Ordered block: genre → BPM (number) → 2-4 specific instruments → vocal tone → mood → production. Add an era/reference to escape the generic default. → references/style-field.md (grab a ready-made per-genre block from references/genre-recipes.md)
  4. Add metatags. Map the structure, then apply the signature move — rich CAPS direction inside each section bracket. Use ( ) for sung ad-libs, [End]/[Fade Out] to close. → references/metatags.md
  5. Deliver. Hand over copy-paste-ready Style, Lyrics (with CAPS brackets), and Exclude blocks, plus mode/toggle and which model the advice assumes.
  6. Iterate. Change ONE variable per regeneration; use Replace/Extend/Cover/Remaster. → references/iteration-and-troubleshooting.md

Field routing (what goes where)

IntentFieldForm
Genre, era, BPM, instruments, vocal tone, productionStyle of Musiccomma-separated, no brackets
The sung wordsLyricsplain lines
Section structure + per-section directionLyrics[ ] tags, CAPS contents
Sung ad-libs / backing echoesLyrics( ), 1-5 words
Sounds to avoidExclude Stylescomma-separated
Fully instrumentalInstrumental toggle + [Instrumental]+ vocals in Exclude

Compact worked example

Style of Music: synth-pop, 1983 neon arcade, 112 BPM, analog synth bass, gated-reverb drums, breathy female vocal, nostalgic and wistful, warm vintage mix

Lyrics:

[INTRO: LONE ANALOG ARP IN AN EMPTY ARCADE, DISTANT COIN SOUNDS, NO DRUMS YET]

[VERSE 1: HUSHED AND INTIMATE, ONE WARM SYNTH AND A SOFT KICK, VOCAL CLOSE TO THE MIC]
Quarter in the slot, the screen lights up my face
Every high score's got somebody's ghost to chase

[CHORUS: EVERYTHING WIDE AND BRIGHT, GATED DRUMS SLAM IN, STACKED HARMONIES, EUPHORIC]
Play me one more life tonight
(one more life)
Neon burning, hold me in the light

[VERSE 2: SAME INTIMATE PALETTE AS VERSE 1]
...
[BRIDGE: DROP TO A SINGLE SYNTH AND VOICE, EXPOSED, ALMOST BREAKING]
...
[CHORUS: BIGGEST YET, ADD A LIVE-CROWD FEEL, MASSIVE FINALE]
Play me one more life tonight
(one more life)
Neon burning, hold me in the light

[OUTRO: LAYERS FALL AWAY BACK TO THE LONE ARP]
[FADE OUT]

Exclude Styles: modern trap hats, autotune, aggressive

Note: every bracket is CAPS direction (signature move); chorus lyrics repeat identically; (one more life) is a sung ad-lib; the outro bookends the intro; closes on [FADE OUT].

When to ask vs. default

SituationAction
Purpose, central emotion, or a liked reference is unknownAsk (high-leverage)
Genre/tempo/vocal unstatedInfer from emotion+purpose, state the assumption
Casual, low-stakes ("just make something fun")Pick strong defaults, generate, refine
Must-include lyrics, names, occasion, clean/explicitAsk if hinted

Reference Files

FileContents
references/intake-and-brief.mdDiscovery questions, vibe→musical-decision translation, brief→fields mapping, propose-back template
references/lyric-craft.mdProsody (stable/unstable), section functions, POV, rhyme types, imagery/verbs, hooks/titles, singability, AI-lyric anti-patterns
references/style-field.mdOrdered-block formula (GMVP), genre vocabulary, BPM ranges, vocal/production descriptors, Exclude field, char limits, version notes
references/genre-recipes.mdCopy-paste Style blocks, BPM, starter structure, and one signature-move bracket for 12 common genres; fusion notes
references/metatags.mdBrackets-vs-parentheses + CAPS rules, structure tags, the signature move (rich CAPS bracket directions), freeform/descriptor/dynamic tags, vocal tags, worked example
references/iteration-and-troubleshooting.mdChange-one-variable loop, edit tools (Replace/Extend/Cover/Remaster/Personas/Stems), instrumental tracks, failure-mode→fix table

Command Palette

Search packages, docs, and navigate Tank