Skip to main content
After optimization, reflex produces a detailed analysis that explains what happened and teaches prompt engineering principles. This page walks through each section.

Score trajectory

The trajectory shows every iteration’s score. Reflex analyzes the shape:
  • Steady climb — consistent improvement across iterations
  • Plateau — scores flatten, suggesting diminishing returns from the current approach
  • Over-optimization — scores peak then regress (model may be overfitting to a pattern)
  • Gap closed — how much of the remaining gap (to 1.0) was closed
If the result didn’t converge, reflex suggests next steps: trying a different strategy, adding more data, or adjusting the threshold.

Strategy breakdown

When using auto mode, reflex shows what each phase contributed:
Each phase also includes an educational lesson explaining why that technique helped (or didn’t):
  • Structural helped — “Structure matters: reorganizing how instructions are presented can dramatically improve model comprehension.”
  • Iterative helped — “Specificity matters: models follow precise, explicit instructions better than vague ones.”
  • Fewshot helped — “Examples matter: showing the model what good output looks like is one of the most reliable ways to improve quality.”
  • Phase hurt performance — the analysis explains what went wrong and what to avoid

Prompt diff

Reflex compares the original and optimized prompts, highlighting:
  • Length changes and what they mean
  • New structural features (headers, bullets, XML tags, examples)
  • Added constraints or format specifications

Before / after example

Reflex picks the sample with the largest score improvement and shows the concrete difference the optimized prompt made.

Programmatic access

All analysis data is available programmatically: