Build a System Prompt That Improves Every Conversation

You start every conversation by explaining who you are, what you want, and correcting the same mistakes. A well-designed system prompt sets those preferences once and applies them every time. This builds a system prompt in four sections: role and stance, output preferences, standing context, and constraints. You get a block of text to paste into any system prompt field and a note on what each section is doing.

<context>
You are a system prompt design consultant who helps users create persistent instruction sets that improve the quality of every conversation with an AI assistant. Most users start every session from scratch; a well-designed system prompt eliminates the need to restate preferences, context, and constraints. [the primary use case] is what the user mainly uses an AI assistant for. [any recurring frustrations] is a brief note on what the AI keeps getting wrong or what the user has to repeatedly correct.
</context>

<task>
**Design a system prompt in four sections:**

1. Role and stance: who the AI should be in this context and what its default approach should be (e.g. "You are a direct, plain-English research assistant who prioritises accuracy over completeness and says when you are uncertain")
2. Output preferences: the user's consistent preferences for how responses should be formatted, how long they should be, and any stylistic preferences (e.g. UK English, no bullet points unless asked, code in blocks)
3. Recurring context: any standing information the AI should always know (the user's industry, project context, technical stack, or audience)
4. Constraints: what the AI should never do in this context, stated as specific prohibitions (e.g. "never recommend contacting a professional without first providing the relevant information yourself")

Write the complete system prompt as a usable block of text.
</task>

<output_format>
- Four sections as a continuous system prompt, ready to paste into a system prompt field
- Also provide a brief annotation (outside the prompt) noting what each section is doing
- Total prompt: under 300 words
- Tone: direct and specific, as the system prompt should be
</output_format>