← All articles· Prompt Engineering

System Prompts Explained: Control AI Behavior Like a Pro

Written by Saad AAI Expert Instructor with experience at Deloitte, PwC, BMO, and Microsoft. Teaching 24,318+ students worldwide.View the Complete AI Bootcamp →March 8, 202515 min read

System prompts let you set the rules for how AI responds. Learn how to write effective system prompts for ChatGPT and Claude with real examples.

System Prompts Explained: Control AI Behavior Like a Pro

Developer working on AI configuration on a computer screen
Developer working on AI configuration on a computer screen

You have been using ChatGPT, Claude, or Gemini for weeks — maybe months. You are getting decent results. You know how to write a clear prompt, how to ask follow-up questions, and how to iterate on responses. But there is a feeling you cannot shake: the AI keeps forgetting your preferences. Every new conversation, you start from scratch. You repeat the same instructions over and over. And sometimes, the AI just does not behave the way you want it to.

There is a tool that fixes all of this, and most beginners either do not know about it or do not understand how to use it properly.

It is called a system prompt.

System prompts are one of the most powerful features in modern AI tools — and once you understand how they work, you will never go back to prompting the old way. Think of it as giving the AI its job description, personality, and ground rules before it starts working. Instead of explaining what you want in every single message, you set it once and it applies to everything.

In this guide, we are going to break down exactly what system prompts are, how they work across different AI platforms, and how you can use them to control AI behavior like a professional. We will include practical examples, templates, and advanced techniques you can start using today.

Let us dive in.

---

What Exactly Is a System Prompt?

At the most basic level, a system prompt is a special set of instructions that tells an AI model how to behave throughout an entire conversation. It sits "above" your regular messages — it is not part of the back-and-forth chat. Instead, it acts as a persistent set of rules that the AI follows no matter what the user asks.

Here is a simple way to think about it.

Imagine you are hiring someone for a job. Before they start working, you give them:

  • A job title ("You are a customer service representative")
  • Rules to follow ("Always be polite, never give refunds without manager approval")
  • How to communicate ("Use a friendly, professional tone")
  • What to avoid ("Never share internal pricing documents")

That is exactly what a system prompt does for AI. It defines the role, the rules, the tone, and the boundaries — before any conversation begins.

System Prompts vs. User Prompts

This is where beginners get confused, so let us make the distinction crystal clear.

User prompt: This is what you type into the chat. Your questions, requests, and instructions. This is the conversation itself.

Example: "Write me a product description for a leather wallet."

System prompt: This is a behind-the-scenes instruction that shapes how the AI responds to every user prompt. The user might never see it.

Example: "You are a luxury copywriter who specializes in high-end fashion accessories. Always use sophisticated, aspirational language. Keep descriptions under 100 words. Never use the word 'cheap' or mention discounts."

When both are active, the AI combines them. The system prompt sets the behavior, and the user prompt provides the specific task. The result is a response that follows the system prompt's rules while addressing the user's actual request.

Think of it this way: the system prompt is the employee handbook and the user prompt is the daily task assignment. The employee follows the handbook rules while completing whatever specific task they are given each day.

---

How System Prompts Work in Different AI Tools

Each major AI platform handles system prompts slightly differently. Let us walk through the big three.

ChatGPT (OpenAI)

In ChatGPT, the consumer version offers system-prompt-like functionality through Custom Instructions and GPTs.

Custom Instructions let you set two things:

  • "What would you like ChatGPT to know about you?" — This is your context (who you are, what you do, your preferences)
  • "How would you like ChatGPT to respond?" — This is your behavior instruction (tone, format, length preferences)

These persist across all conversations until you change them.

GPTs (previously called "Custom GPTs") take this further. When you create a GPT, you write a full system prompt that defines the bot's personality, knowledge, capabilities, and limitations. This is the closest thing to a true system prompt in the consumer ChatGPT experience.

If you are using the OpenAI API, you get direct access to the system prompt through the `system` role in your messages array. This gives you full control.

Claude (Anthropic)

Claude offers system prompts through multiple channels.

In the Claude.ai consumer app, you can set a system prompt at the start of any conversation using the "Set a style" or through Projects where you can define project-level instructions that apply to all conversations within that project.

In the Claude API, you pass a `system` parameter directly — giving you clean, explicit control over the system prompt.

Claude is known for following system prompts particularly faithfully, which makes it a favorite for applications where precise behavior control matters.

Gemini (Google)

Google's Gemini offers system instructions through Gems (custom AI personas) in the consumer product, similar to ChatGPT's GPTs.

In the Gemini API, you can set system instructions that define the model's behavior for the entire conversation.

The core concept is the same across all platforms — you are giving the AI its operating instructions before the conversation starts. The interface just varies.

---

Practical System Prompt Examples

Theory is useful, but examples are better. Let us look at five real-world system prompt examples across different use cases.

Example 1: Customer Service Bot

```

You are a friendly, professional customer service representative for GlowNaturals, an organic skincare brand.

Your responsibilities:

  • Answer questions about our products, shipping, and return policy
  • Help customers choose the right products for their skin type
  • Handle complaints with empathy and offer solutions

Rules:

  • Always maintain a warm, helpful tone
  • If a customer asks for a refund, collect their order number and email, then tell them the refund team will follow up within 24 hours
  • Never make promises about specific results from our products
  • If you do not know something, say "Let me check on that for you" rather than guessing
  • Never discuss competitor products
  • Keep responses concise — under 150 words unless the customer needs detailed help

Our return policy: 30-day returns on unopened products. Opened products can be returned within 14 days if there is a reaction or defect.

Our shipping: Free shipping on orders over $50. Standard shipping is 5-7 business days. Express is 2-3 business days for $9.99.

```

Notice how this system prompt includes the role, tone, specific rules, and actual business information the AI needs. The bot will handle customer conversations naturally while following these guidelines consistently.

Example 2: Writing Assistant

```

You are a writing assistant for a freelance content writer who creates blog posts and articles for small business clients.

Your writing style guidelines:

  • Write in a conversational, approachable tone — like explaining something to a smart friend
  • Use short paragraphs (2-3 sentences max)
  • Avoid jargon unless writing for a technical audience
  • Prefer active voice over passive voice
  • Never use cliches like "in today's fast-paced world" or "at the end of the day"
  • Use specific examples and data points instead of vague claims

Formatting rules:

  • Use H2 and H3 headings to break up content
  • Include bullet points for lists of 3 or more items
  • Add a brief TL;DR at the top of articles over 1000 words

When asked to write, always ask clarifying questions about the target audience and goal before starting — unless these have already been specified.

```

Example 3: Coding Helper

```

You are a senior software developer who helps junior developers write better code.

Guidelines:

  • Always explain your code with clear comments
  • When suggesting a solution, first explain the approach in plain English, then show the code
  • If there are multiple valid approaches, briefly mention the alternatives and explain why you chose the one you did
  • Prioritize readable, maintainable code over clever one-liners
  • When debugging, walk through the logic step by step
  • Always consider edge cases and mention them

Tech stack context: The user primarily works with React, TypeScript, Node.js, and PostgreSQL. Default to these technologies unless specified otherwise.

Code formatting:

  • Use TypeScript by default
  • Follow consistent naming conventions (camelCase for variables, PascalCase for components)
  • Include error handling in all examples
  • Add type annotations

Ready to master AI?

Our Complete AI Bootcamp covers prompt engineering, ChatGPT, MidJourney, vibe coding, AI agents and more — with 110+ video lessons and 2,000+ prompts.

Never write code without explanation. The goal is to teach, not just to provide solutions.

```

Example 4: AI Tutor

```

You are a patient, encouraging tutor who helps beginners learn about artificial intelligence and prompt engineering.

Teaching approach:

  • Start with the simplest explanation possible, then add complexity if the student wants more detail
  • Use real-world analogies to explain technical concepts
  • Ask the student questions to check their understanding before moving on
  • Celebrate progress and correct mistakes gently
  • If a student seems confused, try explaining the same concept a different way rather than repeating yourself

Language:

  • Use simple, everyday language
  • Define any technical term the first time you use it
  • Avoid acronyms unless you have already explained them
  • Keep sentences short and clear

Audience: Your students are smart, motivated adults who are new to technology. Many are from South Asia. They may not have a technical background, but they are eager to learn.

Always end your explanations with a quick check: ask the student if the explanation made sense or if they would like you to clarify anything.

```

Notebook with AI learning notes and a laptop on a wooden desk
Notebook with AI learning notes and a laptop on a wooden desk

Example 5: Business Strategy Advisor

```

You are a practical business strategy advisor for small business owners and solopreneurs.

Your approach:

  • Focus on actionable, low-cost strategies that can be implemented immediately
  • Prioritize revenue-generating activities over theoretical frameworks
  • Always consider the user's resource constraints (limited budget, small team, limited time)
  • Give specific recommendations, not generic advice
  • When suggesting a strategy, include a rough timeline and first three steps

Rules:

  • Never recommend strategies that require significant upfront investment unless specifically asked
  • Always ask about the user's current revenue, team size, and biggest challenge before giving strategic advice
  • Be direct and honest — if an idea sounds bad, say so diplomatically but clearly
  • Back up recommendations with reasoning, not just opinions

Format responses as:

  • Clear recommendation
  • Why it works
  • Step-by-step implementation
  • Expected timeline to see results
  • Potential risks or downsides

---

How to Write an Effective System Prompt

Now that you have seen examples, let us break down the principles for writing your own system prompts that actually work.

Principle 1: Define the Role Clearly

Always start by telling the AI who it is. A clear role gives the model a framework for all its responses.

Weak: "Help me with writing."

Strong: "You are a senior copywriter specializing in email marketing for e-commerce brands."

The more specific the role, the more consistent and expert the responses.

Principle 2: Set the Tone and Communication Style

AI can write in virtually any style — but only if you tell it which one. Be explicit about tone, formality level, and communication preferences.

Consider specifying:

  • Formality (casual, professional, academic)
  • Personality (witty, serious, warm, direct)
  • Vocabulary level (simple, technical, industry-specific)
  • Communication style (concise, detailed, Socratic)

Principle 3: Establish Rules and Boundaries

Rules prevent the AI from going off-track. Think about:

  • What should the AI always do?
  • What should the AI never do?
  • How should it handle situations it is not sure about?
  • Are there specific topics or actions that are off-limits?

Principle 4: Provide Necessary Context

Include any background information the AI needs to do its job well. This might include:

  • Business information (what you sell, who your customers are)
  • Technical context (your tech stack, your platform)
  • Existing guidelines (brand voice documents, style guides)
  • Relevant policies (return policy, pricing structure)

Principle 5: Specify Output Format

Tell the AI how to structure its responses. This saves you from reformatting everything manually.

---

System Prompt Template

Here is a reusable template you can adapt for any use case:

```

ROLE:

You are [specific role with relevant expertise]. Your primary goal is to [main objective].

TONE AND STYLE:

  • Communicate in a [adjective] tone
  • [Additional style guidelines]
  • [Vocabulary or language preferences]

RULES:

  • Always: [things the AI should consistently do]
  • Never: [things the AI should avoid]
  • When uncertain: [how to handle ambiguous situations]

CONTEXT:

[Relevant background information the AI needs]

OUTPUT FORMAT:

  • [How responses should be structured]
  • [Length preferences]
  • [Formatting requirements]

ADDITIONAL INSTRUCTIONS:

[Any other specific guidelines]

```

Copy this template, fill in the brackets, and you have a solid system prompt for virtually any use case. Keep it focused — a system prompt that tries to cover everything often ends up being too complex for the AI to follow consistently.

---

Advanced System Prompt Techniques

Once you are comfortable with basic system prompts, here are some advanced techniques to take your results even further.

Chain of Thought Instructions

You can tell the AI to think through problems step by step before responding.

"Before answering any question, first think through the problem step by step in a brief internal analysis, then provide your answer. Show your reasoning process."

This is especially powerful for analytical tasks, math problems, and complex decision-making.

Few-Shot Examples in System Prompts

Include 2-3 examples of ideal responses directly in your system prompt. This gives the AI a concrete pattern to follow.

"Here is an example of the kind of response I want:

User: What is machine learning?

Response: Machine learning is teaching a computer to learn from experience — kind of like how you learned to catch a ball. Nobody gave you a physics equation. You just threw and caught hundreds of times until your brain figured out the pattern. Machine learning works the same way, except with data instead of baseballs."

Few-shot examples are incredibly effective because they show rather than tell. The AI picks up on the style, length, tone, and structure from the examples.

Conditional Behavior

You can create system prompts that adapt based on the type of question.

"If the user asks a factual question, provide a concise, direct answer with a source. If the user asks for creative content, be more expressive and take creative risks. If the user asks for advice, first ask one clarifying question before responding."

This creates a more intelligent, context-aware assistant.

Persona Layering

Combine multiple traits to create a nuanced persona.

"You are a blend of a patient teacher, a practical consultant, and a motivational coach. When explaining concepts, you are patient and thorough. When giving recommendations, you are direct and action-oriented. When the user seems discouraged, you are encouraging and help them see progress."

This creates more natural, human-like interactions compared to a flat, one-dimensional persona.

---

Custom Instructions vs. System Prompts

You might be wondering: are Custom Instructions (in ChatGPT) the same as system prompts? Not exactly.

Custom Instructions are a consumer-friendly version of system prompts. They are simpler, apply globally to all your conversations, and have limited space. Think of them as "system prompt lite."

System prompts (in the API or in tools like Claude's Projects) are more powerful. They can be conversation-specific, much longer, and more detailed. They give you fine-grained control.

Here is when to use each:

  • Custom Instructions — Great for personal preferences that apply to everything (your writing style, your background, format preferences)
  • Conversation-level system prompts — Better for specific tasks or projects that need unique behavior
  • API system prompts — Essential for building products, bots, and automated workflows

If you are just getting started, Custom Instructions are the easiest entry point. As you advance, you will naturally want the control that full system prompts provide.

---

Limitations of System Prompts

System prompts are powerful, but they are not magic. Here are some honest limitations you should know about.

They are not unbreakable. A determined user can often get an AI to ignore or work around system prompt instructions. This is called "jailbreaking" or "prompt injection." If you are building a product, do not rely on system prompts alone for security.

They have length limits. Very long system prompts can cause the AI to lose track of specific instructions. The sweet spot is usually between 200-800 words. If your system prompt is over 1000 words, consider whether everything in it is truly necessary.

They can conflict with user prompts. If a user prompt directly contradicts the system prompt, the AI has to decide which to follow. Most models prioritize the system prompt, but behavior is not always predictable in edge cases.

They do not give AI new capabilities. A system prompt cannot make an AI access the internet, run code, or do things it fundamentally cannot do. It can only shape how the AI uses its existing capabilities.

They need testing. A system prompt that looks perfect on paper might not produce the results you expect. Always test with diverse inputs and edge cases before relying on a system prompt in production.

---

Getting Started: Your Action Plan

Here is your practical action plan for implementing system prompts starting today:

Step 1: Set up Custom Instructions. If you use ChatGPT, go to Settings and fill in your Custom Instructions. If you use Claude, create a Project with instructions. Start simple — just your background and basic preferences.

Step 2: Create one task-specific system prompt. Pick your most common AI task (writing emails, coding, brainstorming, whatever it is) and write a focused system prompt for it using the template above.

Step 3: Test and iterate. Use your system prompt for a full week. Note what works and what does not. Refine the prompt based on real usage.

Step 4: Build a library. Over time, create a collection of system prompts for different tasks and contexts. Save them somewhere accessible. This becomes your personal AI toolkit.

Step 5: Go advanced. Once you are comfortable, experiment with chain-of-thought instructions, few-shot examples, and conditional behavior. These techniques will push your results to the next level.

---

The Bottom Line

System prompts are the difference between using AI as a generic chatbot and using it as a precision tool that behaves exactly how you need it to. They are not complicated — they are just intentional. Instead of hoping the AI understands what you want, you tell it explicitly.

The best professionals using AI today all have one thing in common: they have invested time in crafting system prompts that make AI work the way they need it to. And now you have everything you need to do the same.

Start simple. One system prompt. One use case. See the difference it makes. Then build from there.

If you want to learn more about prompt engineering, system prompts, and practical AI skills — from the absolute basics to advanced techniques — check out the courses at [seekhoai.pk](https://seekhoai.pk). We break down everything step by step so you can start getting real results, no matter your technical background.

You have the knowledge. Now go put it to work.

Written by Saad A

AI Expert Instructor with experience at Deloitte, PwC, BMO, and Microsoft. Teaching 24,318+ students worldwide.

Ready to master AI?

Our Complete AI Bootcamp covers prompt engineering, ChatGPT, MidJourney, vibe coding, AI agents and more — with 110+ video lessons and 2,000+ prompts.

Related Articles