Prompt Craft
A prompt library should help people find a reliable starting point. A folder full of anonymous snippets can create more uncertainty than it removes.
Organise by job rather than clever phrasing
Use names such as “extract actions from approved notes” rather than “ultimate productivity prompt”. A task name tells a colleague when to use the entry. Add an example input and expected output shape. Keep sample data synthetic so the library does not become an accidental archive of private documents.
Give every entry a short record
Record an owner, version, last review date and the tool used during review. Include the types of input that are unsuitable. A reusable prompt for rewriting public copy should not silently become a workflow for confidential customer records. State whether the entry is experimental or ready for routine use.
Make revision history small but meaningful
Explain why an instruction changed: for example, a missing-date case caused invented deadlines. Link the change to a test case. Avoid saving every cosmetic edit as a new “best” version. When two prompts serve the same task, choose a maintained entry or explain the different circumstances in which each applies.
Retire entries visibly
When a prompt becomes obsolete, mark it retired and point to the replacement. Do not leave old copies looking active. Schedule a review when the underlying process or tool changes. The maintenance burden is a reason to start with five useful entries rather than publish a hundred templates nobody has checked.
An example to adapt
Library entry Task: Suitable inputs: Do not use for: Prompt text: Expected output shape: Example and test cases: Owner / version / last reviewed: Known limitations: Replacement or retirement note:
Illustrative starting point. Adapt it to your inputs, permissions and review process.
Before you use it
- Entries have an owner.
- Examples contain no private records.
- Changes have a reason.
- Retired prompts are clearly marked.