Ultimate Prompt Library Curator

Transform scattered prompts into a world-class prompt library with advanced categorization, quality scoring, and performance tracking

The Prompt

You are a master prompt library curator with experience in information architecture and AI optimization. Create a comprehensive prompt library system:

## LIBRARY ARCHITECTURE

1. **Taxonomy Design**
   - Create hierarchical category structure
   - Define tagging standards
   - Establish naming conventions
   - Set quality criteria

2. **Prompt Evaluation Framework**
   Rate each prompt on:
   - Clarity (1-10)
   - Versatility (1-10)
   - Output consistency (1-10)
   - Model compatibility
   - Token efficiency

3. **Library Features**
   Design systems for:
   - Quick search and retrieval
   - Prompt versioning
   - Usage analytics
   - Team collaboration
   - Export/import capabilities

4. **Quality Assurance**
   - Testing protocols
   - Performance benchmarks
   - Update schedules
   - Deprecation policies

5. **Growth Strategy**
   - Collection expansion plan
   - Community contribution guidelines
   - Prompt discovery methods
   - Integration opportunities

Context: [Describe your prompt library goals and current collection size]

How to Use This Prompt

1. Start by auditing your existing prompt collection
2. Group similar prompts to identify patterns
3. Create a consistent naming scheme (e.g., category-function-version)
4. Build a simple spreadsheet or database to track prompt performance
5. Set up regular review cycles to update and improve prompts

Example Input

Current collection: 150 mixed prompts across Google Docs and Notion
Goals: Organize for team of 20, track performance, ensure consistency
Main uses: Content marketing, customer support, product development

Example Output

Your Prompt Library Transformation Plan

Phase 1: Audit & Organize (Week 1-2)

Current State Analysis:

• 150 prompts identified
• 38% duplicates or near-duplicates
• 92 unique, valuable prompts
• 5 main use categories emerged

Recommended Structure:

Prompt Library/
├── Content Marketing/
│   ├── Blog Writing/
│   ├── Social Media/
│   ├── Email Campaigns/
│   └── SEO Optimization/
├── Customer Support/
│   ├── Ticket Responses/
│   ├── FAQ Generation/
│   └── Escalation Handling/
├── Product Development/
│   ├── Feature Descriptions/
│   ├── User Stories/
│   └── Documentation/
├── Analytics & Reporting/
└── Team Management/

Phase 2: Standardization (Week 3)

Naming Convention: [Category]-[Function]-[Version]-[Date] Example: CONTENT-BlogSEO-v2.1-2024

Metadata Template:

ID: CNT-001
Name: SEO Blog Post Generator
Category: Content Marketing
Tags: [seo, blog, long-form]
Difficulty: Intermediate
Tokens: ~150
Success Rate: 87%
Last Updated: 2024-01-15
Best Models: [GPT-4, Claude-2]

Phase 3: Quality Framework

Scoring Rubric:

• Clarity: Instructions unambiguous? (Weight: 30%)
• Flexibility: Adaptable to variations? (Weight: 25%)
• Output Quality: Consistent results? (Weight: 35%)
• Efficiency: Token usage optimal? (Weight: 10%)

Performance Tracking:

• Weekly usage reports
• User satisfaction scores
• Output quality audits
• Model comparison tests

Phase 4: Implementation Tools

Recommended Setup:

1. Database: Airtable or Notion database
2. Version Control: Git for prompt history
3. Analytics: Simple dashboard for usage stats
4. Sharing: Team workspace with access controls
5. API: Future integration possibilities

When This Prompt Is Most Useful

Use this prompt when you need help with library curator but do not want a generic answer. It works best for operators, founders, automation builders, and teams turning repeated work into a reliable AI-assisted process who already have some context and want the AI to organize it into a workflow map, SOP, automation checklist, prompt chain, or human review plan. The prompt is intentionally written to slow the model down: it asks for the goal, missing information, assumptions, reasoning, and a review checklist instead of jumping straight to a polished answer.

This is especially useful when the task has tradeoffs. A simple prompt may produce a confident answer that sounds good but misses constraints. This version makes the model surface those constraints before it gives recommendations, which makes the output easier to edit, verify, and reuse.

Inputs to Prepare

Before running the prompt, gather:

• The real goal or decision you are trying to support
• The audience, customer, learner, stakeholder, or user involved
• Any source material the AI should use instead of guessing
• Constraints such as deadline, format, budget, word count, platform, or policy
• Examples of good and bad outputs if you have them
• The exact tone you want the final answer to use

For this page, the most important context is: trigger, inputs, systems involved, decision points, review owner, failure cases, and what should happen after output is generated. If you leave that out, the model may still respond, but the result will usually be generic.

Example Input

Workflow: turn support tickets into weekly product insights. Inputs: tags, plan, ticket text. Output: themes, quotes, and follow-up tasks.

How to Review the Output

Do not use the first answer blindly. Check whether it:

• makes handoffs and ownership explicit
• defines what the AI should not decide
• includes monitoring or review checkpoints
• makes assumptions visible instead of hiding them in confident language
• gives you something you can act on, test, or revise within the same work session

If the answer feels generic, reply with: “Make this more specific to my context. Remove generic advice, name the tradeoffs, and show the exact changes you would make.” If the answer is too long, ask for a shorter version that keeps the checklist and decision points.

Common Failure Modes

• Too little context: the AI fills gaps with generic advice.
• No review criteria: the output sounds polished but is hard to judge.
• Unclear audience: the answer may optimize for the wrong reader or use the wrong tone.
• Overclaiming: the model may invent certainty when the source material is weak.

The fix is to add concrete inputs and ask for assumptions, alternatives, and review criteria before you use the final output.

Practical Variations for Ultimate Prompt Library Curator

• SOP mode: Ask for trigger, input, output, owner, and acceptance criteria for each step.
• Automation mode: List systems involved and ask where AI should draft, classify, summarize, or route work.
• Monitoring mode: Ask for quality checks, failure signals, and human review points.

Follow-Up Prompts

Use these after the first answer:

• “Rewrite this using only the context I provided. Label assumptions instead of hiding them.”
• “Give me a conservative version, a direct version, and a version optimized for speed.”
• “Create a final review checklist I can use before I publish, send, ship, or present this.”

What Makes This Page Different

This page is useful when you are working on library curator and need more than a blank chat box. It gives you a starting prompt, context checklist, review criteria, and practical variations so the answer can be tested instead of merely accepted. If your task is broader, start with a workflow guide first, then come back to this prompt once the input, audience, and success criteria are clear.