Development criteria
It turns the relationships and states of tracks, albums, and playlists, key user flows, recovery paths, and completion conditions into an implementable specification.
MUSIC PROMPTS
Music and audio website prompts
How should a Music and audio site be designed? Model the relationships and states of tracks, albums, and playlists first, then treat continuous playback and queue control as a primary risk. Each service guide below combines an implementation specification with design standards.
- Primary goal
- listening and discovery
- Core entities
- tracks, albums, and playlists
- Design risk
- continuous playback and queue control
10 REAL SERVICES
Music and audio · 10 real services
Development prompts and DESIGN.MD for 10 real services designed around listening and discovery.
ANSWER GUIDE
Music and audio How to choose a prompt
Choose the service whose core screen and repeated behavior most closely match the product you are building. Apply only information priority and state design, never the reference brand assets.
Design criteria
Start from A music interface for Music and audio, centered on tracks, albums, and playlists, with a [reference] brand impression led by [color], while avoiding the original logo, proprietary copy, images, and pixel-level layout.
Risk to validate
Treat continuous playback and queue control as a primary design risk and define loading, empty, error, partial-data, and success states.