How to name prompts so a library stays searchable
A prompt library becomes unmanageable when names describe projects instead of reusable tasks. A better convention combines the task, output format, and important constraint: `extract_invoice_json_strict`, `rewrite_release_notes_plain_language`, or `classify_ticket_priority_v2`.
Keep human-readable titles in metadata, but use stable identifiers for files and API references. Add a short purpose statement, expected inputs, expected outputs, model assumptions, owner, and revision number.
Dates are useful in the changelog, not in the primary name. Otherwise every edit creates a new-looking prompt and hides the relationship between versions.
- Category
- Product
- Platform
- Web