Rule 01
Tested
Someone has to use it for real work before it publishes. A clever draft that never left a chat window does not count.
AboutEditorial, not infinite
A prompt library built the slow way.
Most prompt libraries are technically full and practically unusable. This one is smaller on purpose: every entry tested, attributed, and versioned.
Origin
It started in a Notes app.
A hundred and forty prompts. No titles. No dates. No way to find the good meeting-notes one when you actually needed it.
The useful question was not how to organise that file. It was why nearly every prompt library ends up in the same state. Three reasons, in the order they bite:
- 01Nothing is tested, so half the entries never really worked.
- 02Nothing is attributed, so there is nobody to ask when one breaks.
- 03Nothing is versioned, so when behaviour shifts you cannot tell whether the prompt changed, the model changed, or you did.
We publish roughly a third of what arrives. The rejections are almost never about effort.
The bar
Three rules. That is the whole policy.
Every prompt on PromptsBuddy has to clear all three. Miss one and it stays out.
Rule 02
Attributed
A person stands behind it. When the prompt breaks, there is someone to ask. Anonymous paste dumps are how libraries rot.
Rule 03
Versioned
When the text changes, the change is visible. Silent edits destroy trust. You should always know what you are running.
Boundaries
What we will not build
Saying no is part of the product. These are permanent.
- 01
No upvotes or leaderboards
Popularity ranking optimises for the screenshot, not for the ninth time you use something. The ninth time is the only one that matters.
- 02
No streaks or daily nags
We will not gamify a library. Attention theatre is not editorial judgment.
- 03
No scrubbing the limits
Every prompt carries a line about where it falls down. Removing those would make the catalogue look better and work worse.
What lives here
Three surfaces. One standard.
- Browse prompts
The library
Prompts as specifications: variables pulled out, working shown, limitations kept in public.
- Read the writing
The blog
Field notes on what actually holds across model versions, and what was always theatre.
- Hear an episode
The podcast
Clear episodes on real workflows: how prompts get used at work, not how they demo on stage.
How it is made
A directory, rendered.
Every prompt, article, and episode is a plain file. Contributions arrive through the form and get run cold by a human before they land. If something here is wrong, tell us and we will fix it.
Who runs it
Maintainers and contributors.
A small group of maintainers and a growing set of contributors. Nobody does this full time. If you want in, the door is documented and open.
Next step
Use a prompt, or add one.
Start in the library. If you have something you rely on most weeks, put your name on it and send it in.