What this prompt does
This prompt has Claude or ChatGPT design a podcast website and player interface. You set [podcast_name] and [podcast_genre], then describe the [episode_count], the [release_schedule], the [monetization] model, the [platforms] you distribute on, and the [framework]. The model designs the landing page, the episode directory, the episode detail page, a persistent audio player, a host or network dashboard, and the framework implementation.
It works because a podcast site is really an audio app: the persistent player and transcript-synced playback are the hard parts, and the prompt designs them up front. By naming [episode_count] and [release_schedule], the model designs directory grouping and pagination that suit a 120-episode, four-season catalog. The [monetization] variable shapes premium-episode gating and sponsorship placement, and the framework section specifies audio handling, continue-where-you-left-off, and keyboard shortcuts.
When to use it
- You're building a podcast website where your own site is the primary listening destination.
- You want a persistent bottom-bar player with queue, speed control, and resume designed.
- You need an episode directory with season grouping and transcript search.
- You're designing episode pages with timestamped show notes and a synced transcript viewer.
- You want premium subscriber episodes and sponsorship placement accounted for.
- You need a host dashboard for publishing, scheduling, and per-episode analytics.
Example output
The model returns a component-by-component design document. The landing page is specified with a showreel-style hero player, "listen on" buttons, featured episodes, and a newsletter lead magnet. The episode detail page covers a full player with 0.5x-3x speed, timestamped show notes that jump playback, and a transcript that auto-scrolls with audio. The persistent player section details a mini-to-full expand, queue reordering, a sleep timer, and keyboard shortcuts. The closing [framework] section adds audio-library handling, resume via storage, and host-dashboard analytics. Expect a detailed spec, not finished code.
Pro tips
- Set
[episode_count]realistically so the directory uses sensible season grouping and pagination instead of one long list. - Use
[monetization]to switch premium gating and sponsorship slots on, since they change the player and episode page. - Name your real
[platforms]so the "listen on" buttons and RSS link match where you actually publish. - Keep the transcript-sync requirement explicit — synchronized auto-scroll and timestamp jumps are the standout feature.
- Pin
[framework]to your audio library so the persistent-player and resume notes are usable. - Ask the model to expand the host dashboard if publishing workflow and retention analytics matter most.
