Prompt Design Guide

Public

Good prompts are explicit, structured, and testable. Treat them as code: version, review, and evaluate regularly.

Structure

  • System instruction: purpose, constraints, tone.
  • Few-shot examples: diverse and representative.
  • Output schema: JSON with strict fields or clearly delimited sections.

Guardrails

  1. Refuse ambiguous requests; ask clarifying questions.
  2. Redact sensitive inputs before echoing content.
  3. Decline tool use outside approved domains.
Tip

Keep a minimal baseline prompt and measure deltas when iterating. Small, controlled changes lead to faster learning.

Related docs