Prompts

Use two prompt surfaces with distinct jobs.

Surface	Put this here
`prompt`	The task, domain knowledge, constraints, persona, and tool rules
`conversation.prompt`	How the exchange should feel: pacing, clarification style, and when to be more or less conversationally active

Task prompt

Describe what success means. Keep business rules here so the foreground agent and application tools share one clear job.

123const prompt = `Help the user reconcile an equipment checklist.
Ask only for missing information.
Confirm ambiguous item names before writing them.`;

Conversation prompt

Describe preferences, not algorithms.

12345const conversation = {
  prompt: `Keep the exchange energetic but concise.
  Let the user list several related items without repeatedly stopping them.
  Ask a short clarification when a value is genuinely ambiguous.`,
};

Avoid writing timing thresholds, audio rules, model instructions, or transcript-repair logic. Live Voice owns those behaviors. Your conversation prompt should express the experience you want.

If an instruction changes what the agent does, put it in prompt. If it changes how the exchange flows, put it in conversation.prompt.