Reusable Prompt Systems

Template-driven prompting improves consistency at scale. Separate static policy instructions from dynamic request context - the same separation of concerns you apply to code and configuration.

Template Structure That Scales

# template: ticket-triage v3.2
SYSTEM (static, versioned):
  You are a support triage assistant for {{product_line}}.
  Always output strict JSON: {"priority", "team", "reason"}.
  Escalate security reports regardless of wording.

USER (dynamic, per request):
  Ticket: {{ticket_text}}
  Customer tier: {{tier}}
  Recent related incidents: {{incident_context}}

What Goes Where

Operational Rules

• Keep immutable system constraints in one template - never string-concatenate policy in scattered code paths.
• Inject context as typed variables and validate them before rendering (length limits, encoding, injection screening).
• Track template version and test score for each release - a template change is a deploy, not an edit.
• On Bedrock, Prompt Management can store, version, and A/B prompt variants as first-class resources.