AI Podcast Producer

AI Prompts to Build This

Copy these build prompts into Claude, Cursor, or your AI coding tool. Create a free account to unlock the full research behind them.

1. 1. Project Setup

   Build the weekend MVP of "PodcastPilot": drop in a raw recording and get a cleaned master, chaptered show notes and titles.
   
   Stack: Next.js (App Router), TypeScript, Tailwind, Supabase (Postgres, Row Level Security, Storage, Auth with email magic link), Deepgram for word-level transcription, ffmpeg in a small separate Node worker, Claude (Anthropic API) for the show notes. Deploy the app on Vercel.
   
   Tables (Row Level Security on, each user reads only their own rows):
   - shows(id, user_id, name, bible_text, loudness_target)
   - episodes(id, show_id, status, duration_sec, raw_path, master_path, transcript_json)
   - cuts(id, episode_id, start_ms, end_ms, type, accepted)  where type is one of filler, silence, manual
   - assets(id, episode_id, kind, path, meta_json)  where kind is one of notes, chapters
   
   Screens: /login, /shows, /episodes/[id] (waveform with cut markers and the kit).
   Env vars (names only): NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY (server only), DEEPGRAM_API_KEY, ANTHROPIC_API_KEY.
   
   Do not build: billing, plans or metered hours, audiograms, a video timeline, a job queue service, Cloudflare R2.
   Done when: npm run dev starts, the worker can run ffmpeg, you can sign in, and the four tables exist with Row Level Security on.

2. 2. Core Feature

   Build the one feature that proves PodcastPilot: raw tape in, a cleaned master and a publish kit out.
   1. On upload, store the raw file in Storage and create an episode with status processing.
   2. Transcribe with Deepgram and keep the word timestamps.
   3. Detect filler words and silences longer than 1.2 seconds and write cuts rows.
   4. In the worker, apply the accepted cuts with ffmpeg and normalize loudness to the show's target, then write the master.
   5. Ask Claude, using the show bible, for show notes, 8 to 12 chapters, 3 titles and 5 pull quotes. Save them as assets.
   6. Set the status to review. The episode page shows the waveform with cut markers, a bulk Accept fillers button, and a Regenerate notes button that does not re-run the audio.
   Rules: this is audio production, not a video editor, and never return a meeting-style action-item list.
   Empty state: with no shows, show the form that creates a show and its bible.
   Done when: a 10-minute test recording gives a master with the accepted cuts applied, chapters, three titles and show notes.

3. 3. Landing Page

   Build a one-page landing site for PodcastPilot, an audio production tool for indie podcasters.
   Hero: "Raw tape in. Episode kit out." Sub: "Filler gone, levels fixed, show notes written. You keep the jokes." One button: Drop a sample file, which joins the waitlist.
   Sections: the Sunday-night editing spiral, how it works in four steps (ingest, clean the master, generate the publish kit, style the next episode), a sample kit, and an FAQ saying plainly that this is audio production, not a YouTube editor and not a Zoom notes tool.
   Waitlist: store the email in a waitlist table in Supabase. No other service.
   Style: Geist, a dark studio background, one lime or lavender accent.
   Done when: the page renders on a phone and a submitted email appears in the waitlist table.

4. 4. Branding Package

   Use a design or image tool for this one. A coding agent cannot draw a logo.
   Brand for PodcastPilot: a wordmark and an icon that suggest a waveform with a clean cut.
   Colors: a dark studio background, off-white and one lime or lavender accent. Type: Geist for the interface and a mono for timestamps.
   Deliverables: wordmark, icon, a cut-marker style for the waveform, and one launch graphic.
   Done when: each deliverable is saved in one folder and the icon reads at 32 px.