prompt-library-builder

Prompt-Library Builder

If you use AI regularly, you retype variations of the same requests constantly — the email rewriter, the meeting summarizer, the code explainer. A prompt library captures your best versions once, parameterized and organized, so you invoke them instead of reinventing them. This builds yours: identifies your recurring tasks, turns them into reusable templates, and sets up a system to store and improve them — a toolkit that gets more valuable every time you add to it.

What This Skill Produces

• Your recurring tasks, captured — the AI requests you make repeatedly, identified and listed
• Reusable prompt templates — each turned into a clean, parameterized template (clear role, the inputs to fill in, and the desired output format) instead of a one-off
• An organization scheme — a simple way to categorize and find prompts (by task, by domain, by frequency)
• The reusability principles — what makes a prompt reusable and reliable (specific role, explicit inputs, defined output, examples where helpful)
• A storage & improvement system — where to keep them (a doc, snippets, a tool) and how to refine each as you use it
• A starter set — a few of your most-used prompts, templated and ready

Required Inputs

Ask for these if not provided:

• Your recurring AI tasks — the things you ask AI to do often (or a prompt to help surface them)
• A few examples — prompts you've written that worked, to templatize
• Your tools — where you'll store/use them (a notes app, snippet manager, the AI tool itself)
• Your domains — work, personal, coding, writing (for organizing)

Framework: Capture, Templatize, Organize

1. Find the repeats. Identify the requests you make again and again — these are the highest-value candidates to templatize.
2. Templatize for reuse. Turn each into a clean template: a clear role/instruction, the variable inputs to fill in [like this], and the output format you want — so it works every time with just the specifics swapped.
3. Add what makes it reliable. Specific instructions, an output format, and an example or two where the task is fuzzy — the difference between a prompt that mostly works and one that always does.
4. Organize for retrieval. A simple scheme (by task type or domain) so you can actually find the right prompt when you need it — a library you can't search is a graveyard.
5. Store where you'll use it. Match storage to your workflow (a snippet tool, a doc, saved prompts) so invoking one is faster than rewriting.
6. Improve continuously. Refine each template as you notice what's missing — and add new ones as new repeats emerge. The library compounds.