System Prompt Architecture

# System Prompt Architecture

## The Pattern
A strong system prompt is the operating contract for a coding agent. It should define mission, scope, boundaries, and quality expectations before any task-specific instruction appears.

Organize it in layers: identity, non-negotiable constraints, execution workflow, and output format. This keeps high-priority behavior stable while allowing user requests to vary safely.

For coding work, the architecture should explicitly cover repository hygiene, tool usage, verification habits, and communication style. This shape is inspired by production AI coding assistants that must stay consistent across many sessions.

## Why It Works
- Reduces ambiguity by making priorities explicit from the start.
- Prevents instruction conflicts through a predictable rule hierarchy.
- Improves output consistency across different tasks and users.
- Makes audits easier because behavior is tied to named sections.

## Prompt Template