What it is for
instructions.prompt on a template sits once at the top of the template and applies to every section inside it. Two jobs:
- One place for cross-section instructions. Anything that applies to every section in this template — guidance you’d otherwise have to paste into every section’s
contentPromptormiscPrompt— lives here once. - Domain & use-case priming. A single sentence telling the model what kind of note this is, the specialty, the care setting. Cheap to write; sharpens every section’s output downstream.
Examples
A minimal, effective template prompt is just one sentence:Where it sits in the prompt hierarchy
The template prompt has lower priority than the section’s owninstructions — if a section’s contentPrompt, writingStylePrompt or miscPrompt says one thing and the template prompt says another, the section wins. But the model reads the template prompt before the section’s writingStylePrompt and outputSchema descriptions, so it acts as a frame the rest of the prompt fills in.
| Priority | Surface |
|---|---|
| 1 (highest) | Section instructions — contentPrompt, writingStylePrompt, miscPrompt |
| 2 | Template instructions.prompt ← this recipe |
| 3 | outputSchema descriptions and typed constraints |
Anti-patterns
- Don’t restate what the template sections already clearly prompt for.
- Don’t bury per-section rules here. If only the HPI section needs a rule, put it in HPI’s
contentPromptormiscPrompt. The template prompt is for rules that apply to every section. - Keep it limited and simple. Long template prompts compete with section-level instructions for attention. If it’s growing, the rule probably belongs in a specific section.
Related
- Recipe 1 — contentPrompt — per-section scope.
- Recipe 2 — writingStylePrompt — per-section voice.
- Create a Template — where
instructions.promptlives in the template create body.