Creating a Prompt Library

Cheryl — I've helped run one of these on an innovation team, and DShaw is right: the structure is the whole game. A few things I'd add from watching one survive past the first month:

1. Organize by task, not by tool. People think "I need a better quiz question" or "I need a hero image," not "I need a Rise code block prompt." If the library matches how people think about their work, they actually browse it.

2. Seed it yourself first. Launch with 10–15 prompts that already produce good output, example included. An empty library that asks 20 people to contribute on day one stays empty — nobody wants to be the first to write in it.

3. Date-stamp everything. Prompts go stale as models change — what worked in January produces different output by June. A quarterly pass to retire duds keeps the library trustworthy. A library nobody trusts is a library nobody opens.

A shared doc or wiki is honestly enough for the first version. DShaw's tool looks solid for later, but tools don't fix an empty or stale library — the habits do.