Build a Prompt Library That Actually Works
Part 5 of 11 — A Practical Guide to Claude Setup
Most people treat prompts like Google searches. They don’t put much thought into their prompts. It’s just something written so fast that it could be scribbles on a sticky note.
They write something that works, use it once, and never find it again. The next time they need something similar, they reach for the “sticky note” and start from scratch. Meanwhile, the prompt that produced that one great output is buried in a conversation from three weeks ago.
That’s not a system that scales.
CLAUDE_PROMPTS.md is your prompt library. This is a structured collection of your best, most-used prompts, built to be reused and improved over time.
The RIPEN Framework
Before you get started, I want to share my favorite framework for writing prompts. You need structure. A good prompt isn’t a question. It’s a brief and the best briefs follow a consistent architecture.
The RIPEN framework:
R — Role
What role should Claude play? Specific roles produce specific output. “Act as a senior program evaluator with experience in workforce development” produces different output than “help me with this.”
I — Instructions
What exactly should Claude do? Be precise. “Write a 700-word newsletter section” is better than “write something about this topic.”
P — Parameters
Constraints and specifications. Tone, length, format, what to include, what to avoid. The more specific your parameters, the less Claude has to guess.
E — Examples
If you have examples of what good output looks like, include them. Examples are worth a thousand words of instruction. Show Claude the target.
N — Notes
Anything that doesn’t fit elsewhere. Background context, exceptions to the rules, special considerations for this prompt.
What Goes in the File
CLAUDE_PROMPTS.md is organized by use case. Each entry follows the RIPEN format. You build it over time. Don’t feel as if you have to fill it in all at once.
Start with your five most-repeated tasks. For most knowledge workers, those are something like:
Drafting a specific type of content (newsletter, report, proposal)
Summarizing a long document
Reviewing something for quality or consistency
Generating questions or frameworks for a meeting or workshop
Translating something complex into plain language for a specific audience
Build one RIPEN-structured entry for each. Test it. Refine it. Add it to the library.
I’ve built a tool that you can use to build a RIPEN prompt just by answering a few questions. Give it a try!
https://ripen.donbarger.com
The Compounding Effect
Here’s the great thing about a prompt library. It gets better over time.
Every time a prompt produces output you love, you refine it. Every time it misses, you diagnose why and update the parameters. After a few months, your prompt library reflects your actual judgment and taste and not just some generic instructions.
Think of this as the compound interest of your AI setup. You invest time upfront building good prompts and every future use of those prompts pays a dividend. The return grows as the prompts improve.
A Fictional Example
Meet David. He runs communications for a global non-profit. One of his most-used prompts is for drafting internal briefings for senior leadership.
Here’s his RIPEN-structured entry:
Role: Senior communications strategist with 15 years of non-profit experience. You understand that non-profit executives receive dozens of briefings per week and have limited time.
Instructions: Write an internal briefing on [topic] for senior leadership. Lead with the most important point. Use the pyramid structure: conclusion first, evidence second.
Parameters: Maximum 400 words. Three sections: Summary (2 sentences), Key Points (3 bullets), Recommended Action (1 specific ask). No jargon. Active voice throughout.
Examples: [David has pasted in two strong examples briefings he wrote himself]
Notes: Our leadership reads on mobile, so short paragraphs. They respond better to specific asks than open-ended options.
When David loads this prompt and adds the topic, the first draft is 80% done. He’s not starting from scratch. He’s refining.
Calling a Prompt
With the file loaded, activation is simple:
“Load CLAUDE_PROMPTS.md and use the [briefing] prompt for this topic: [topic].”
No setup. No rewriting the brief from memory. The library does the work.
Starter Template
# Prompt Library — [Your Name]
## How to Use
Each prompt follows RIPEN: Role, Instructions, Parameters, Examples, Notes.
Activate with: "Load CLAUDE_PROMPTS.md and use the [prompt name] prompt."
---
## Prompt: [Name]
**Role:** [Who should Claude be?]
**Instructions:** [What should Claude do?]
**Parameters:**
- Length: [target]
- Tone: [description]
- Format: [structure]
- Avoid: [what not to include]
**Examples:** [Optional — paste strong examples]
**Notes:** [Additional context]
Next: Article 06 — two voices, one person. The internal communication file that will speed up your work.
