Structuring System Prompts
Quick start
Collect or infer:
- •Agent purpose and primary use cases
- •Required capabilities and tools
- •Behavioral constraints and guardrails
- •Context sources and injection points
- •Voice and tone requirements
Then produce output using TEMPLATES.md. Validate with RUBRIC.md.
Workflow
- •Define agent identity and core purpose
- •Establish capability boundaries and tool access
- •Structure behavioral rules by priority (critical → preferred)
- •Design context slots and injection points
- •Specify output format requirements
- •Add examples for ambiguous behaviors
- •Optimize for token efficiency without losing clarity
- •Run the rubric check. Revise until it passes.
Degrees of freedom
- •Low: Critical sections (identity, guardrails) must follow established patterns
- •Allowed variation: Section ordering; example verbosity; formatting style
Failure modes to avoid
- •Conflicting instructions at different prompt levels
- •Critical rules buried in verbose sections
- •Over-specification that prevents helpful behavior
- •Under-specification that allows unsafe behavior
References
- •Templates: TEMPLATES.md
- •Rubric: RUBRIC.md
- •Examples: EXAMPLES.md
- •Prompt architecture: reference/prompt-architecture.md
- •Section patterns: reference/section-patterns.md