agentleFS
frankxaifrankxai/creator-skills/skills/music/suno-prompt-architect/SKILL.md

suno-prompt-architect

Skill6 starsChanged 47 days agoMITView on GitHub

Convert a finished creative brief and lyrics into a precise Suno Custom Mode packet: title, style, exclusions, structure/performance tags, pronunciation notes, and one controlled alternate. Use before any Suno browser generation.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 11 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not prompt from a vague mood alone when the full workflow is requested.

    line 11
  2. Very specific:

    If lyrics are part of the work, run lyric-composer first.

    line 18
  3. Distinctive:

    Write one compact natural-language paragraph in priority order:

    line 34
  4. Distinctive:

    Use semicolons to separate layers.

    line 40
  5. Distinctive:

    Use clean tags and whitespace.

    line 48
  6. Distinctive:

    Do not add production prose between every lyric line.

    line 72
  7. Distinctive:

    No named artists, bands, songs, labels, franchises, or cloned voices.

    line 80
  8. Distinctive:

    No contradictory genre, tempo, vocal, or energy instructions.

    line 81
  9. Distinctive:

    No impossible precision disguised as control.

    line 82
  10. Distinctive:

    No more than one main vocal persona.

    line 83
  11. Distinctive:

    Create an alternate only when it tests one useful variable, such as:

    line 91
  12. Distinctive:

    Keep hook, lyrics, and emotional contract fixed.

    line 96
  13. Very specific:

    Before browser execution, write the packet into the run's style-prompt.md and run the taste gate.

    line 109
  14. Very specific:

    Read the relevant modules in …

    line 113

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Suno Prompt Architect

Input requirement

Do not prompt from a vague mood alone when the full workflow is requested. First establish:

  • listener/use case;
  • emotional start → turn → ending;
  • song form and duration intent;
  • lyric or instrumental status;
  • sonic thesis and negative space.

If lyrics are part of the work, run lyric-composer first. For meditations, run guided-meditation-composer and prefer a separate instrumental bed.

Build this exact packet

TITLE

Concrete, memorable, easy to pronounce. Usually 1–5 words. Avoid generic mood labels.

MODE

  • Custom Mode: on.
  • Instrumental: on only for a true instrumental/meditation bed.
  • Model: choose the newest stable model visible in UI at execution time.

STYLE

Write one compact natural-language paragraph in priority order:

<genre/fusion and era attributes>; <emotional state>; <BPM/meter/pocket>; <focal instruments and negative space>; <vocal persona/delivery or no vocals>; <section dynamic journey>; <mix/spatial character>; <ending>.

Use semicolons to separate layers. Prefer specific verbs and acoustic behavior over long adjective lists.

EXCLUDE STYLES

List only the highest-risk drift: 3–8 concise exclusions.

LYRICS / STRUCTURE

Use clean tags and whitespace. Put performance cues in the section heading only when needed. Example:

[Intro - sparse, 4 bars]

[Verse 1 - close, conversational]
...

[Pre-Chorus - rising]
...

[Chorus - open, harmonized]
...

[Bridge - stripped]
...

[Final Chorus - full lift]
...

[Outro - intimate hard stop]
...

Do not add production prose between every lyric line.

PRONUNCIATION NOTES

List only risky names, numbers, acronyms, multilingual words, or deliberate stretched vowels. Apply phonetic fixes directly in the lyrics after approval.

Prompt checks

  • No named artists, bands, songs, labels, franchises, or cloned voices.
  • No contradictory genre, tempo, vocal, or energy instructions.
  • No impossible precision disguised as control.
  • No more than one main vocal persona.
  • Style and lyrics describe the same dynamic arc.
  • Exclusions do not negate the positive prompt.
  • The strongest words appear early.
  • The ending is specified.

Controlled alternate

Create an alternate only when it tests one useful variable, such as:

  • pulse: free-time vs 72 BPM;
  • texture: organic acoustic vs glassy electronic;
  • vocal delivery: restrained close-mic vs open ensemble chorus.

Keep hook, lyrics, and emotional contract fixed. State the single variable changed.

Final delivery

Return:

  1. recommended title;
  2. full copy/paste STYLE field;
  3. EXCLUDE STYLES field;
  4. complete LYRICS field (or instrumental, no vocals);
  5. pronunciation notes;
  6. one-sentence reason this packet serves the brief;
  7. optional one-variable alternate.

Before browser execution, write the packet into the run's style-prompt.md and run the taste gate.

Shared fundamentals and provider boundary

Read the relevant modules in https://github.com/frankxai/agentic-music-producer-os/blob/18dc9bee02001befb3a2a3bd7747b78f798dff13/docs/MUSIC-FUNDAMENTALS.md, then https://github.com/frankxai/agentic-music-producer-os/blob/18dc9bee02001befb3a2a3bd7747b78f798dff13/docs/PROVIDER-CAPABILITIES.md and https://github.com/frankxai/agentic-music-producer-os/blob/18dc9bee02001befb3a2a3bd7747b78f798dff13/docs/MUSIC-FACTORY-CONTRACT.md when selecting tools or executing production. Canonical public source: https://github.com/frankxai/agentic-music-producer-os. The craft precedes the provider packet.

Suno v6 is the documented baseline checked 2026-10-01; capture the actual account model, settings, limits and credit cost before operating. No official public generation API was verified. Preserve the approved lyrics across adapters. Score/text analysis and a prompt review do not prove audio quality. Record real listening and measurements separately; keep unknown values null. Personal preferences and artist canon remain in their owner project.

For MiniMax Music 3, translate section tags to their own lines; never share inline Suno performance tags blindly. For Eleven Music, use a prompt or a chunk plan and preserve exact approved lyric text. For Lyria, treat duration and harmony as requested direction. These are separate provider packets, not Suno endpoints.

Resolve docs/... paths from the repository root, not from the skill folder. If using only this skill outside a checkout, read the same named documents from the canonical public source.

Current craft and production integration

Checked 2026-10-01. Use the public music fundamentals, provider register and factory contract. They cover harmony/voice leading, groove, motif, prosody, hooks, form, vocals, arrangement, low end, mixing, measured delivery, provenance and durable jobs. Load only the modules needed for this task.

Keep local artist/persona canon, identity, preferences and account entitlements scoped to this project. Shared craft does not assign a singer or overwrite canon. Select the current account-visible Suno model (documented baseline v6); no official public Suno generation API was verified. Lyria, Eleven Music and fal MiniMax Music 3 have separate documented API routes and constraints. A skill or MCP tool is not a connected generation account.

Preserve approved lyrics across adapters. Prepare, authorize/reserve, submit, reconcile, archive, listen, measure, attest rights and stage release separately. Bind receipts to exact contract/asset hashes. Never infer audio quality, measured BPM, playback, rights or publication from a text review or completed job. Unknown paid submissions remain held for reconciliation; no blind rerender.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.