From a one-off prompt to a workflow your team reuses
Most good prompts are written once, used once and lost in a chat history. Someone on the team figures out exactly how to get a clean cold email or a sensible sprint summary out of a model — and a week later everyone else is still typing "write me an email about…".
A case on CatchCase is our answer to that. It's a prompt that has been turned into a small, repeatable tool.
What makes a prompt reusable
Look at a prompt that worked for you and underline everything that would change next time: the product name, the audience, the tone, the data you pasted in. Everything else — the instructions, the structure, the constraints — is the part worth keeping.
That split is the whole idea. The stable part becomes the case; the changing parts become placeholders written in square brackets:
Write a launch email for [PRODUCT] aimed at [AUDIENCE].
Tone: [TONE]. Keep it under 150 words and end with one clear call to action.
When you open a case, every placeholder turns into a field in the Run this case form. You fill in three short answers instead of rewriting the prompt, press Run, and the finished result appears in a chat where you can keep refining it.
Anatomy of a good case
A title that is a job, not a topic. "Write a cold email sequence" beats "Email marketing". People scan the library looking for the thing they need to get done today.
One sentence on the outcome. What will the reader have in their hands after running it? "A five-email sequence with subject lines, ready to paste into your outreach tool."
Placeholders for everything that varies — and nothing else. Three to six is the sweet spot. Name them the way a colleague would ask: [JOB_TITLE], [PAIN_POINT], [MEETING_NOTES]. Names containing words like NOTES, TEXT or DATA get a larger text box automatically.
Steps, briefly. Three to five lines explaining how to use the result: where to paste it, what to check, what to tweak. Steps are what make a prompt a workflow.
An honest time estimate. "Saves 45 minutes" is only useful if it's true. Don't round up.
Why runnable matters
Copying a prompt into another tool works, but it leaks value at every step: you forget to replace a placeholder, you lose the result in a different app, you can't share how you got there.
Running a case on CatchCase keeps all of it together. The filled-in prompt, the answer and every follow-up live in one chat. You can attach files — the meeting notes, the brief, last quarter's CSV — and keep asking questions about them. You only pay for what the model actually uses.
Turn your best prompt into a case
- Take a prompt you've used at least three times.
- Replace every changing detail with a
[PLACEHOLDER]. - Run it yourself with two very different inputs. If one of them produces something odd, the fixed part of the prompt is still too specific.
- Write the title, the one-sentence outcome and three steps.
- Submit it. We review every case before it's published and credit you as the author.
The best cases in the library started exactly like this — as someone's private trick that worked too well to keep to themselves.