Prompt Library
Overview
A prompt library stores reusable prompts that consistently produce useful engineering output.
Why It Matters
Reusable prompts save time and improve quality by capturing what works.
Core Concepts
- Good prompts are specific.
- Good prompts include constraints and examples.
- Good prompts ask for reviewable output.
Mental Models
Think of prompts as interfaces. The better the input contract, the better the result.
Best Practices
- Capture proven prompts.
- Include the task, context, and desired output format.
- Keep prompts short enough to reuse.
Common Mistakes
- Storing generic prompts no one uses.
- Forgetting to update prompts when the workflow changes.
- Mixing too many goals into one prompt.
Trade-offs
More prompt detail can improve output, but too much can make prompts brittle.
Decision Framework
| Prompt type | Best for |
|---|---|
| Drafting | Structured writing |
| Review | Code or text critique |
| Extraction | Summaries and checklists |
Examples
- “Review this diff for bugs, regressions, and missing tests.”
Checklists
- Is the prompt specific?
- Does it define the output shape?
- Is it reusable?
Senior Engineer Notes
Senior engineers keep a small library of prompts that consistently improve signal, not a giant pile of one-off experiments.