Bottom line:Playlist quality depends more on prompt constraints than model brand; define context, exclusions, and format up front.

Why this approach works

Most weak AI playlists come from under-specified prompts. When the prompt lacks constraints, outputs drift toward generic popular songs.

A stronger method is to define scenario, exclusions, version preference, and strict output format before generation.

Then run a pilot set first, validate quickly, and expand only after direction is correct.

Execution workflow

1. Define scenario variables (time, context, energy curve).
2. Set constraints (language ratio, era, exclusions, version preference).
3. Force output format: one line per song, "Song - Artist" only.
4. Test with a small pilot list, then scale and import to Apple Music.

Copy-ready Prompt Template

Use this as a base and replace scenario variables:

你是我的音乐策展助手。请为“周五晚下班开车回家（约40分钟）”生成 18 首歌单。

约束：
1) 语种比例：中文 60%，英文 40%
2) 风格：前段舒缓 -> 中段提速 -> 尾段收束
3) 年代：2010-2026
4) 禁用：不要纯音乐，不要翻唱版优先
5) 版本偏好：优先录音室原版
6) 避免同一歌手连续出现

输出格式（严格）：
- 每行一首，格式为“歌名 - 歌手”
- 不要编号，不要解释，不要分组标题

Support Boundaries (important)

Playlist-link import supports Spotify, YouTube Music, Deezer, NetEase, QQ Music, KuGou, and Qishui/Douyin (douyin.com entry). Single-link conversion supports Spotify, YouTube Music, Deezer, and NetEase only; QQ Music, KuGou, and Apple Music links return unsupported.

Frequently Asked Questions

How many songs should I generate first?

Start with 15-20 as a pilot. Expand only after direction is validated.

Why enforce "Song - Artist" output?

It reduces ambiguity and improves import matching quality.

Should I optimize for one model only?

Not necessarily. Keep one master structure and tune model-specific phrasing.

Is small mismatch after import normal?

Yes. Cross-platform licensing/version differences are expected.

Continue Reading (AI Playlist Hub)

• AI Playlist to Apple Music (Main Guide)
• Text-to-Playlist Import Guide
• Playlist Sync Troubleshooting
• ClipTunes
• Song Link Converter