KorinAI

Prompt Templates

A prompt template is a reusable instruction block you can paste into agents or chats. It can include placeholders (e.g., [goal], [audience]) and optional sections (style, constraints, examples) to standardize tone and structure across teams. Placeholders are not auto‑replaced—fill them manually when you use the template.

Overview

Prompt Templates help you:

  • Define a reusable prompt body with placeholders (e.g., [goal], [audience]).
  • Set guidance sections (style, constraints, evaluation) to improve output quality.
  • Share templates across agents for consistent responses.

Getting Started

  1. Open Dashboard → Settings.
  2. Go to the Prompt Templates tab (within Settings).
  3. Click New Template to open the modal and provide:
    • Title
    • Content (the full prompt body)
  4. Save. Your template appears in the list where you can Edit (pencil) or Delete.
  5. Use templates in two ways (manual paste/edit — no auto‑replacement):
    • Agent Settings → General: incorporate template content into Persona or Instructions for consistent behavior.
    • Your Agents: when creating child agents, reuse templates to seed persona/behavior.
    • In Chat: paste a template and manually replace any placeholders (e.g., [audience]).

Template Structure

  • Body
    • Main instruction with placeholders, e.g.,
    text
    You are a helpful assistant. Objective: [goal].
Audience: [audience].
Output a concise, structured response.
  • Sections (optional)
    • Style guide (voice, tone, formatting)
    • Constraints (what to include/exclude, length)
    • Examples (few-shot pairs)

Note: The current UI supports a simple Title + Content model. There is no automatic placeholder substitution. If you include tokens like [audience], you must manually replace them when inserting the template into Persona/Instructions or when pasting into the Chat UI.

Examples

  • Writing brief

    • Variables: goal, audience, length (enum: short/medium/long)
    • Body:
    text
    Goal: [goal]
Audience: [audience]
Length: [length]
Structure into: Summary, Key Points, Next Steps.

  • Bug triage

    • Variables: title, steps, expected, actual, severity (enum)
    • Body:
    text
    Classify and summarize the bug report.
Title: [title]
Steps: [steps]
Expected: [expected]
Actual: [actual]
Severity: [severity]
Return: Summary, Category, Priority, Suggested Owner.

Best Practices

  • Keep variables minimal and well-described; add defaults where possible.
  • Separate “guidance” (style/constraints) into sections to avoid cluttering the body.
  • Prefer enums for finite choices (tone, length, severity) to standardize output.
  • Test templates with sample values; iterate to reduce ambiguity.
  • Keep prompts concise; put longer rules in separate sections or link to internal knowledge.

Related Topics

Previous
← Agent Orchestration