Free, ungated, and actually usable.
8 templates you fill in, 42 prompts across 7 stages of the job, and 3 teardowns you read one screen at a time. No form, no email to download, free whether or not you ever pay for anything.
Documents, filled in
Each one has a worked example written for a real company, and the trap that ruins that section.
One per stage of the job
Long, structured prompts worth keeping, each with the specific way the model lets you down.
Case studies you scroll
One beat at a time, with the screen pinned beside the writing and the principle named.
Blank documents are the easy part.
Anyone can publish a PRD with four headings in it. What is missing from every template on the internet is what good looks like in each section, so every one of these carries a filled example and the mistake that section attracts.
The PRD that survives contact with engineering
One page. Four sections engineers actually read before they start arguing about scope.
The signal log
One row per quote. A structured way to hold raw feedback without losing the exact words.
The opportunity tree, on one page
Outcome, opportunity, solution, experiment. The map from what you're chasing down to what you're testing this week.
The experiment brief
The hypothesis, the metric, the sample, and the rule for stopping, all written before the test runs, not after.
The launch checklist
Everything that has to be true before a feature goes to everyone, with a name and a date on every line.
The eval set
The golden case sheet for an AI feature: the input, what a good answer looks like, how you'd grade it, and the real failure it came from.
The one page decision memo
What is broken, who it hurts, what you'd do about it, and how you'd know it worked. One page to a founder.
The user interview guide
A discovery guide built on what people actually did, not what they say they'd do next.
Prompts for each stage of the job.
Not one line tricks. These are the long, structured prompts that are worth saving, and every one names the specific way the model fails at that task, because that is the part you have to catch.
Discovery prompts
Research and talking to users, with a model doing the first pass.
Analysis prompts
Turning evidence into a claim you'd defend in a room.
Spec prompts
Writing it down so it survives contact with engineering.
Design prompts
Interface, flows, and the copy that sits inside them.
Build prompts
Shipping it, and catching what breaks on the way.
Launch and growth prompts
Getting a feature in front of everyone, and reading what happens next.
Career prompts
Portfolio, interviews, and surviving the first ninety days somewhere new.
Case studies you read one screen at a time.
Public commentary on products you already use. The screen stays pinned while the writing moves, the callouts land on the part being discussed, and each beat names the principle underneath it.
One lesson. A reason to return.
Explore Duolingo's published streak redesign, the trade-off behind the reported retention lift, and an experiment for your own product.
One thing per page
The least fashionable design decision in government, and why it beats every clever form you have ever seen.
Selling the thing you cannot imagine
IKEA Place did not make furniture easier to browse. It removed the one doubt that stops people buying furniture online.
These are public teardowns of public behaviour, written without any involvement from the companies named. The screens are drawings rather than screenshots, and nothing internal is claimed.