Glossary
System prompt
The long, persistent instructions given to an LLM that define its role, behavior, constraints, and tone. Distinct from the per-turn user message, which is just the immediate request.
A system prompt is the persistent instruction set given to an LLM that defines its role, behavior, constraints, output format, tone, and any guardrails. It's sent with every request and acts as the "operating system" the model runs against.
Distinction from user messages:
- System prompt. "You are a senior customer support agent at Acme. You answer technical questions about our API. You only answer from official docs. If unsure, escalate. Tone: friendly but precise."
- User message. "How do I authenticate to your API?"
The system prompt is durable. The user message is the immediate request.
Anatomy of a production-grade system prompt:
- Role definition. Who the agent is.
- Task scope. What it should do.
- Constraints + boundaries. What it should NOT do.
- Output format. How responses should be structured.
- Examples. Few-shot demonstrations of good outputs.
- Tone + voice. How it should sound.
- Escalation rules. When to defer to a human.
- Tool documentation. What tools it has access to + when to use each.
Example
Solidus's Teardown agent has a system prompt encoding three positioning frameworks (Dunford's 5-step canvas, Jobs-to-Be-Done, Ries+Trout category ownership), strict no-fluff rules (no "in today's competitive landscape"), required source citation, and structured JSON output schema. About 1,800 words. The prompt IS the product — the same Claude model with a generic prompt produces wildly worse audits.
Apply this
Get a real automation audit on your business.
Pay $4,500, fill an intake, get a Claude Opus-written strategic roadmap inside a week.
Start the audit →