Productive— faster every day
For your professionTeachersStudentsManagersMarketingDevelopersFreelancersParents

Prompt library · AI · 12 prompts

Prompts from the guide

AI music: stings and background tracks without licensing headaches… almost

12 prompts from this guide. Fill in whatever sits in [square brackets] — your own context, the document text or the name of your tool. That context is exactly what separates a generic answer from a usable one.

Read the full guide →

Before you start: a brief, not a vibe

Help me put together a music brief for a music generator.

Project: [description — e.g. a series of how-to videos for a
furniture maker]
Where the music will be used: [opening sting / bed under narration /
transitions between chapters]
Length: [15 s sting, 2:30 bed]
Target audience: [who'll be watching]
The brand sounds like: [3 adjectives — e.g. calm, hands-on, matter-of-fact]
What's happening under the music: [male voiceover, calm speaking
pace, shots of hands at work]

Don't give me generic advice. Return:
1. Five musical directions that would fit — for each, the genre,
   instruments, tempo in BPM, mood, and why it suits the project
2. One sentence per direction on where it could go wrong
3. Three things the music must NOT contain, given what's happening
   underneath it
4. Which direction to try first, and why

Template: a bed under a voiceover

Instrumental bed under a voiceover, genre ambient / minimal.
Tempo around 75 BPM, calm, no strong rhythm.
Instruments: gentle piano, muted string pad, subtle bass line.
Mood: focused, matter-of-fact, mildly optimistic, not sentimental.
Structure: soft build over 6 seconds, then a stable plateau with
no dramatic shifts, ending fades out gently. Length roughly
2 minutes 30 seconds.

No vocals and no vocal-style pads of any kind.
No drums and no percussion.
No strong melodic line that would pull attention away.
No sudden dynamic shifts and no orchestral finale.
Keep the mix airy, leave the midrange clear for a human voice.

Template: a sting

Short podcast sting, genre modern acoustic electronic.
Length 8 seconds. Tempo 110 BPM, brisk but not frantic.
Instruments: acoustic guitar with short notes, a soft synth pad,
one subtle percussion hit at the start.
Mood: friendly, matter-of-fact, clever — not corporate, not
cheerful to the point of goofy.
Structure: a recognizable 4-note motif right in the first second,
the motif repeats, a clean resolved ending (not a fade out).

No vocals. No orchestra. No fanfare.
The motif has to be memorable after a single listen.

A background bed under video and presentations

Background bed under a company presentation running with a live
speaker.
Genre: minimalist electronic with acoustic elements.
Tempo 85 BPM, steady, no speeding up. Length 4 minutes.
Instruments: pad, muted electric piano, a subtle low-end foundation.
Mood: professional, calmly confident, not triumphant.
Structure: an even plateau with no peaks, so it can be freely cut
and looped, ending fades out gradually.

No vocals, no solo instruments, no strong melody.
No percussion that would set a pace against the speaker's.
Nothing that could be called “tense” or “emotional.”

Music for an app or game

Music loop for a mobile game, screen [main menu / calm
building phase].
Genre: [chiptune with a modern mix / acoustic ambient].
Tempo 100 BPM, steady.
Instruments: [gentle arpeggio, soft bass, subtle music-box bells].
Mood: pleasant, unobtrusive, holds up as background listening for
long stretches.
Structure: a repeatable 30-second loop, start and end in the same
harmony, so they can be joined without an audible seam.

No vocals. No effects that could be confused with in-game sounds.
No standout moments that would grate after the tenth repeat.
Even, consistent dynamics.

Corporate events and internal content

Walk-on music for speakers at a company conference.
Genre: modern orchestral crossover with electronic elements.
Tempo 120 BPM. Length 30 seconds.
Instruments: strings, subtle drums, synthetic bed.
Mood: celebratory, energetic, but not a triumphant fanfare.
Structure: 4-second build, full entrance, stable section of
20 seconds, a clear ending (not a fade out) — so the host knows
exactly when to start talking.

No vocals. No sports-broadcast clichés like stadium drumming.

Selection: listen in context, not in silence

I'm choosing background music for [project description] and have
8 generated variants. I can't judge them objectively.

Put together a listening protocol I can use to score the variants:
- the criteria that actually matter for a bed under a voiceover
- criteria that are just a matter of taste and shouldn't decide it
- a concrete listening procedure (on what device, for how long,
  in what order)
- the trap people typically fall into when choosing music, and
  how to avoid it

Give each criterion a 1–5 scale with a description of what 1 and
5 mean.
Output it as a table I can print.

Editing: extensions, sections, endings

I have a generated track that works, but I need it adapted for
use in a video:
1. Extend it by 40 seconds in the same character, no new instruments
2. A new ending: a gentle fade over 6 seconds, not a hard cut and
   not a fade mid-phrase
3. A version without [percussion] for the section where the guest
   is talking
4. A short 5-second clip from the same material to use as a bumper

Keep the tempo, key, and instrumentation of the original track.

A prompt for lyrics from your brief

Write the lyrics for a short song I'll use as [a sting for a
podcast about home cooking / a farewell message for a colleague
retiring].

Brief:
- Length: roughly [30 seconds of singing], so a short verse and
  chorus
- Language: [English]. Who's singing: [one female voice]
- Mood: [funny, but not cheesy; warm, not sappy]
- Must mention: [the show's name / the colleague's name / three
  specific details]
- Must NOT mention: [anything about age, no jokes about overtime]

Rules:
- Write lyrics that are actually singable: short lines, natural
  word stress landing where a listener would expect it, no
  consonant clusters piling up
- Chorus max 4 lines, and it has to hold up repeated three times
  without getting tiresome
- No generic phrases about journeys, dreams, and stars
- Break the lyrics into sections with tags in square brackets
- At the end, list 3 lines you're not confident are singable, and
  offer an alternative for each

Singability in English

Here's a song lyric I want a music generator to sing:

[paste lyrics]

Review it for singability in English and return:
1. Words and phrases that are hard to sing (consonant clusters,
   long vowels landing on an unstressed beat) — for each, suggest
   a replacement with the same meaning
2. Spots where the natural word stress would land on the wrong
   syllable when sung
3. Lines that are a syllable too long or too short
4. The chorus: is it short and repeatable enough? If not, tighten it

Don't rewrite the whole thing — just flag the spots and offer
alternatives.

Checklist before commercial deployment

Put together a checklist of questions I need to answer in a music
generator's license terms before I deploy a generated track in
[deployment description — e.g. a monetized video on a client's
public channel].

I want a checklist of questions, not answers — I'll find the
answers myself in the current terms. Cover:
- the scope of commercial use by tier
- what happens to the rights after a subscription ends
- whether the license can be transferred to a client
- exclusivity: can someone else get the same track
- any requirement to credit the source or label the content as AI
- rules around monetization and content-recognition systems
- what applies to tracks generated earlier on a different tier
- what to do if someone raises a claim against my content

For each question, note where in typical terms that information
usually lives (section name), and how to recognize an ambiguous
answer that I should get confirmed by support instead of assuming.

Don't describe how specific services actually work — you don't
have current data on that.

Phase 7: when to use a generator and when a stock library

I'm deciding between an AI music generator and a stock library for
this specific case:

Project: [description]
Where it'll run: [public channel / internal / advertising / product]
How long it'll stay live: [one-off / years]
How many tracks I need: [1 / 12 / dozens]
How much sound originality matters: [description]
Who carries the risk if a dispute comes up: [me / the client /
the company]

Build a decision table: for each option (generator, stock library,
composer for hire), give what's in its favor, what's against it,
what risk I'd be carrying, and what I'd need to be able to show
if someone asked.
At the end, give one recommendation and one condition under which
the recommendation would change. Don't list prices — I'll find
those myself.

All prompts