ax-gepa

name	ax-gepa
description	This skill helps an LLM generate correct AxGEPA optimization code using @ax-llm/ax. Use when the user asks about AxGEPA, GEPA, Pareto optimization, multi-objective prompt tuning, reflective prompt evolution, validationExamples, maxMetricCalls, or optimizing a generator, flow, or agent tree.
version	23.0.0

GEPA Optimization Codegen Rules (@ax-llm/ax)

Use this skill to generate GEPA optimization code. Prefer the top-level optimize(...) helper for normal code, and use direct AxGEPA / AxBootstrapFewShot only when the user needs low-level optimizer control.

Use These Defaults

• Use optimize(program, train, metric, { studentAI, teacherAI, ... }) for normal generator and flow tuning.
• Prefer ai(), ax(), and flow() for new code.
• Use a strong teacherAI and a cheaper studentAI.
• Pass validationExamples when you have a holdout set.
• Set maxMetricCalls to bound optimizer cost; optimize(...) defaults it to 100.
• Use scalar metrics for one objective and object metrics for Pareto optimization.
• Apply results with program.applyOptimization(result.optimizedProgram!).
• For tree-wide runs, expect optimizedProgram.componentMap.
• Persist artifacts with axSerializeOptimizedProgram(...) and restore them with axDeserializeOptimizedProgram(...) so the same flow works in browsers and Node.
• optimize(...) runs AxBootstrapFewShot -> AxGEPA for small starter sets by default, preserving the demos in result.optimizedProgram.demos.

Critical Rules

• optimize(...) and AxGEPA.compile() work for a single generator and for tree-aware roots such as flows or agents with registered optimizable descendants.
• There is no separate flow-only GEPA optimizer. Use AxGEPA for flows too.
• The metric may return either number or Record<string, number>.
• Keep metrics deterministic and cheap by default.
• Avoid extra LLM calls inside the metric unless the user explicitly wants judge-based evaluation.
• If the user needs LLM-as-judge scoring for a non-agent GEPA run, prefer a plain typed AxGen evaluator instead of writing a custom judge abstraction.
• maxMetricCalls must be large enough to cover the initial validation pass over validationExamples.
• GEPA optimizes generic string components exposed by getOptimizableComponents(). If a tree exposes no components, optimization will fail.
• Use held-out validation examples for selection. Do not reuse the training set as validationExamples.
• result.optimizedProgram is the easy-to-apply best candidate. result.paretoFront is the full trade-off set for multi-objective runs.
• Direct AxGEPA still has its own bootstrap option, but top-level optimize(...) composes the existing AxBootstrapFewShot optimizer before GEPA instead.

Metric Selection

Choose the evaluation path deliberately:

• Prefer a deterministic metric when correctness can be read directly from prediction and example.
• Prefer a deterministic metric when cost, latency, recursion depth, or tool count matters.
• Use a plain typed AxGen evaluator only when the task is genuinely qualitative and hard to score exactly.
• For agent.optimize(...), prefer the built-in judge path instead of manually wrapping a judge metric. Normal agent users usually do not need to set target or metric at all.

Rule of thumb:

• optimize(...) on AxGen or flow: use a metric first, optionally a plain typed AxGen evaluator if needed.
• agent.optimize(...): use custom metric for crisp scoring, otherwise let the built-in judge handle scoring. Add judgeAI plus judgeOptions only when you want a stronger or separate judge model.

Canonical Scalar Pattern

import { ai, ax, optimize, AxAIOpenAIModel } from '@ax-llm/ax';

const student = ai({
  name: 'openai',
  apiKey: process.env.OPENAI_APIKEY!,
  config: { model: AxAIOpenAIModel.GPT54Mini },
});

const teacher = ai({
  name: 'openai',
  apiKey: process.env.OPENAI_APIKEY!,
  config: { model: AxAIOpenAIModel.GPT54 },
});

const classifier = ax(
  'emailText:string -> priority:class "high, normal, low", rationale:string'
);

const train = [
  { emailText: 'URGENT: Server down!', priority: 'high' },
  { emailText: 'Weekly newsletter', priority: 'low' },
];

const validation = [
  { emailText: 'Invoice overdue', priority: 'high' },
  { emailText: 'Lunch plans?', priority: 'low' },
];

const metric = ({ prediction, example }: { prediction: any; example:  }) =>
  prediction?. === example?. ?  : ;

 result =  (classifier, train, metric, {
  : student,
  : teacher,
  : ,
  : ,
  : ,
  : ,
  : ,
  : validation,
  : ,
});

classifier.(result.!);
.(result.);

Canonical Pareto Pattern

import { ai, flow, optimize, AxAIOpenAIModel } from '@ax-llm/ax';

const student = ai({
  name: 'openai',
  apiKey: process.env.OPENAI_APIKEY!,
  config: { model: AxAIOpenAIModel.GPT54Mini },
});

const teacher = ai({
  name: 'openai',
  apiKey: process.env.OPENAI_APIKEY!,
  config: { model: AxAIOpenAIModel.GPT54 },
});

const wf = flow<{ emailText: string }>()
  .n('classifier', 'emailText:string -> priority:class "high, normal, low"')
  .n(
    'rationale',
    'emailText:string, priority:string -> rationale:string "One concise sentence"'
  )
  .e('classifier', (state) => ({ emailText: state.emailText }))
  .e('rationale', (state) => ({
    emailText: state.emailText,
    priority: state.classifierResult.priority,
  }))
  .( ({
    : state..,
    : state..,
  }));

 train = [
  { : , :  },
  { : , :  },
];

 validation = [
  { : , :  },
  { : , :  },
];

  = () => {
   accuracy = prediction?. === example?. ?  : ;
   rationale =  prediction?. === 
    ? prediction.
    : ;
   brevity = rationale. <=  ?  : rationale. <=  ?  : ;
   { accuracy, brevity };
};

 result =  (wf, train, metric, {
  : student,
  : teacher,
  : ,
  : ,
  : ,
  : ,
  : ,
  : validation,
  : ,
});

 ( point  result.) {
  .(point., point.);
}

wf.(result.!);
.(result.?.);

Metric Patterns

// Scalar objective
const scalarMetric = ({ prediction, example }) =>
  prediction.answer === example.answer ? 1 : 0;

// Multi-objective
const multiMetric = ({ prediction, example }) => ({
  accuracy: prediction.answer === example.answer ? 1 : 0,
  brevity:
    typeof prediction?.reasoning === 'string' &&
    prediction.reasoning.length < 120
      ? 1
      : 0.2,
});

• Return plain numbers or plain object literals.
• Keep objective names stable across calls.
• Prefer normalized scores such as 0..1 so trade-offs are easy to reason about.

Result Handling

const { optimizedProgram, paretoFront } = result;

program.applyOptimization(optimizedProgram!);

// Save for later
const saved = JSON.stringify(optimizedProgram);

// Load later and re-apply
const loaded = JSON.parse(saved);
program.applyOptimization(loaded);

• Single-target runs usually populate both optimizedProgram.instruction and optimizedProgram.componentMap.
• Tree-wide runs rely on componentMap, keyed by full component key.
• Pareto points expose candidate configs under point.configuration.componentMap.

Useful Options

const optimizer = new AxGEPA({
  studentAI,
  teacherAI,
  numTrials: 20,
  minibatch: true,
  minibatchSize: 5,
  minibatchFullEvalSteps: 5,
  earlyStoppingTrials: 5,
  minImprovementThreshold: 0,
  sampleCount: 1,
  seed: 42,
  verbose: true,
});

• numTrials: number of reflection/evolution rounds.
• minibatch: reduce per-round evaluation cost.
• minibatchSize: examples per minibatch.
• earlyStoppingTrials: stop after repeated non-improvement.
• minImprovementThreshold: reject tiny gains below this threshold.
• seed: stabilize sampling during demos and tests.

Budgeting and Validation

• Always create distinct train and validationExamples arrays.
• Size maxMetricCalls for at least one full validation pass plus several rounds.
• If the user wants a strict budget, say so explicitly and set maxMetricCalls.
• For expensive trees, start with auto: 'light' or fewer numTrials, then scale up.
• GEPA selects among exposed components using measured accept/reject history, not LLM-generated numeric scores. The LLM proposes component text; metrics decide whether to keep it.
• Function/tool trace reflection is keyed by stable component IDs where available, so function renames do not break saved candidate maps.

Troubleshooting

• Error about maxMetricCalls being too small: increase it until the initial validation pass fits.
• Empty or poor Pareto front: verify the metric returns numbers for every example.
• No tree optimization effect: ensure child programs are registered under the root and expose optimizable components.
• Saved optimization applies only partly: use program.applyOptimization(...), not just setInstruction(...), so componentMap reaches the full tree.
• Agent target seems too broad: when using agent.optimize(...), set target: 'actor', 'responder', 'all', or explicit program IDs. The wrapper filters GEPA components to the selected target.

Good Example Targets

• /Users/vr/src/ax/src/examples/optimize.ts
• /Users/vr/src/ax/src/examples/gepa.ts
• /Users/vr/src/ax/src/examples/gepa-flow.ts
• /Users/vr/src/ax/src/examples/gepa-train-inference.ts
• /Users/vr/src/ax/src/examples/gepa-quality-vs-speed-optimization.ts
• /Users/vr/src/ax/src/examples/axagent-gepa-optimization.ts