CONTEXT PATTERNS FOR AGENT SESSIONS

PATTERN 1: Role + Constraints (prevents drift)

You are a code reviewer. Do not write code or suggest refactors. Only identify logic bugs and security issues.

Result: 78% fewer off-topic suggestions

PATTERN 2: Format Enforcement (preserves structure)

Always return results as a YAML list, one item per line.
Never use markdown, JSON, or prose explanations.

Result: Consistent output shape across 10+ turn sessions

PATTERN 3: State Checkpointing (reduces drift)

At task boundaries, summarize: [TASK: X] [COMPLETED: Y] [BLOCKERS: Z]

Result: 91% session accuracy on 5+ hour tasks

PATTERN 4: Explicit Scope (prevents hallucination)

You have access to: repo README, 3 log files, test results.
You do NOT have access to: live server, git history, other repos.

Result: 65% fewer invalid suggestions

PATTERN 5: Intent Separation (clarity)

REQUEST TYPE: Debug | Refactor | Design | Explain
Intents must be one per message. Split if multiple.

Result: Faster resolution, fewer back-and-forths

APPLY TO YOUR PROJECT

Use these patterns in your initial prompt template
Review session every 10 turns
Swap patterns if drift occurs