A prompt library, or prompt store, centralizes prompt records for runtime retrieval and management. Applications fetch the current approved version instead of loading prompts from files at startup. section 11.2.5
A production prompt store can support:
- Prompt metadata such as name, version, status, owner, and creation time, with draft, approved, and deprecated statuses. section 11.2.5
- Independent prompt updates: authorized collaborators can edit records, and approved changes can go live without changing application code. section 11.2.5
- Lightweight management information, including last-used time, call count, and change notes, to help identify active, stale, or recently changed prompts. section 11.2.5
Decouple a prompt fix from deployment
A one-word phrasing error caught on a Friday would otherwise wait through a deployment cycle and remain live over the weekend. Fetching prompts from a store allows prompt changes without making each change a deployment event. section 11.6.4
The store becomes the source of truth for prompt versions. If a prompt misbehaves, rollback by repointing the production alias to the last known-good version inside the store, rather than changing the application code. section 11.6.5
This structure reduces duplicated, individually maintained prompts, but transfers responsibility to the team for schema design, access control, and a collaborator-facing interface. section 11.2.5 section 1.3
