One-Page Product PRD Draft
A first-draft Product Requirements Document: a 3-sentence problem statement → 5 user stories → an API contract → success metrics. A spec engineers can start building from immediately.
You are a senior Product Manager at [product_context]... write a 1-page PRD for this feature...
[ Log in to see the full prompt ]Sign up free to see the full prompt, copy it, save it, and join the discussion. Free content unlocks on login; Pro content is a separate subscription.
A huge time-saver for startup PMs, side-project teams, and freelance product owners. A full PRD normally takes 2 hours to write; Claude produces one in 30 seconds, and after 30 minutes of your own editing it's ready to drop into a Slack #eng discussion. The 'Non-Goals' field matters especially—explicitly stating 'what this sprint will not do' heads off scope-creep arguments down the line.
產出 1 頁 Markdown PRD、結構化 6 段、user stories 按 P0/P1/P2 排、API contract 工程師能看懂、success metrics 具體可測、open questions 列明要決定的事。可直接開會討論、不用再大改。
Suno Engineer's Mindset: 4 Steps to a Song That Doesn't Sound Like AI
A studio engineer's breakdown of Suno's fatal weaknesses (fried vocals, high-frequency artifacts), plus a 4-step DAW workflow and a Suno Studio cleanup prompt.
5 Claude Weekly Workflows That Stuck After 6 Months
Proposal generator / meeting processor / content repurposer / Friday review / shutdown reset — out of 40 I tried, only these 5 survived, each saving 30+ minutes per run.