A Library of Proven Wishes

Opening Scene

A wise household doesn’t rediscover the correct wording for a common, recurring wish from scratch every single time the need arises. Once a specific wish has been carefully worded, tested, and proven reliable, it gets written down, kept, and reused — with only the small, specific details changed for each new occasion. That same discipline, applied to prompts, turns individually hard-won lessons into a genuine, compounding organizational asset.

In Plain English

Prompt templates are reusable, well-tested prompt structures with clearly defined placeholders for the parts that change between uses — a template for summarizing a document, a template for extracting structured data, a template for drafting a specific kind of email. Building a library of proven templates avoids re-deriving the same hard-won lessons — structure from Article 5, examples from Article 6, constraints from Article 11 — from scratch every time a similar task comes up.

The Old Way

Before prompt template libraries were common practice, each new prompting task was often approached as if starting from zero:

• Individual practitioners often redeveloped similar prompts independently, without benefiting from lessons already learned elsewhere in the same organization.
• A well-tested prompt’s hard-won refinements often stayed with the individual who developed them, rather than being captured and shared for reuse.
• There wasn’t yet a standard practice of treating a well-crafted prompt as a genuine, valuable, reusable organizational asset.

Building shared template libraries emerged as organizations recognized how much redundant effort informal, individual prompt development was actually costing them.

What’s Changing (and Why AI Is the Reason)

1. Prompt management tooling has matured to support versioning, sharing, and reusing prompt templates systematically across a team or organization, connecting directly to the collaborative practices covered in Article 19.
2. Treating well-tested prompts as genuine, reusable assets — rather than one-off, individually developed artifacts — has become standard, expected organizational practice.
3. This connects directly to the testing and iteration practices covered in Article 13, since a template’s real value comes specifically from having already been tested and proven reliable, not just from being reusable.

The Metaphor, Fully Extended

The Genie’s Lamp	Prompt Template Concept
A carefully worded, proven wish, written down and kept for future use	A well-tested prompt structure, saved as a reusable template
Only the small, specific details changed for each new occasion	Only the placeholder values changed for each new use
A household’s compounding wisdom about what wording actually works	An organization’s compounding library of proven prompt patterns
Rediscovering the same correct wording from scratch, wastefully, every time	Redeveloping similar prompts independently, wastefully, without shared templates

Quick Recap

• Prompt templates are reusable, well-tested prompt structures with clearly defined placeholders for what changes between uses.
• Building a template library avoids redundantly re-deriving the same hard-won lessons for similar recurring tasks.
• Prompt management tooling increasingly supports systematic versioning and sharing of templates.
• Treating proven prompts as genuine organizational assets is now standard, expected practice.

Where This Fits in the Series

Article 17 covered building a reusable library of proven prompts. Article 18 covers how to actually grade whether any given prompt, template or otherwise, is genuinely performing well.