Prompt Optimization
Build Prompt Families that automatically select the best prompt for each input. Create specialized prompts that work together to perform better than any single prompt could.
How Prompt Families Work
Instead of using one prompt for everything, Empromptu creates Prompt Families - collections of prompts that work together. Start with one prompt, and the system helps you build out the whole family.
❌Traditional Approach
Single Prompt → All Inputs → Inconsistent Results
✅Empromptu Approach
Input Analysis → Best Prompt from Family → Optimized Result
4 Optimization Interfaces
Access all interfaces through the Actions button on any task. Each tab handles different aspects of prompt optimization.
📊Event Log
Track every optimization attempt with detailed information:
👥Prompt Family
View and manage your collection of specialized prompts:
🔧Manual Optimization
Step-by-step improvement wizard for targeted enhancements:
⚡Automatic Optimization
Let the system optimize for you with minimal input:
Understanding Optimization Scores
0-10 Scoring Scale
Excellent
Optimal performance, ready for business use
Good
Business-ready, minor edge cases
Acceptable
Improvable but functional
Needs Attention
Moderate issues, requires optimization
Poor
Requires immediate optimization
Score Reasoning Examples
"extracted_completeness - AI response captures the essence and key emotional elements. Summary captures key experiential aspects while maintaining vivid language."
Each score includes detailed reasoning that explains which evaluations passed/failed, specific issues identified, and what contributed to the score.
Optimization Strategies
Start with Automatic
Best for establishing baseline performance and handling common optimization patterns.
Refine with Manual
Best for addressing specific weaknesses and fine-tuning performance.
Building Effective Prompt Families
Include Different Scenarios
- •Different input types (positive/negative content)
- •Different output requirements (brief/detailed)
- •Different edge cases (unusual inputs)
Use Representative Test Data
- •Test data should match real use cases
- •Include edge cases and challenging scenarios
- •Sufficient volume to identify patterns
Monitor Performance Continuously
- •Check Event Log regularly for new patterns
- •Update families as use cases evolve
- •Remove underperforming prompts