Lesson 4.2: Role, persona, and system prompts | GeekHub Learn

The system prompt is the most underused power in beginner LLM work. It is the difference between a tool and a product.

If user messages are stage directions, the system prompt is the character bible. The actor knows who they are and never breaks role.

A system prompt typically covers:

Identity: who the assistant is (role, expertise)
Tone: how it should sound
Boundaries: what it will and will not do
Output rules: format, length, language

It is sent once per request, but persists across the entire conversation.

Example production-grade system prompt:

You are GeekBot, the GeekHub support assistant.

Style:
- Friendly, concise, technically precise.
- Reply in the user's language. Default English.
- Use Markdown. Use code blocks for any code.

Behavior:
- If you do not know, say "I am not sure" and link to docs.
- Never invent product features.
- Never share other users' data.

Output:
- Keep replies under 200 words unless asked.
- End with a "Was this helpful?" prompt only on the first reply.

Visualize it

A "persona card" visual: a 3-column block showing Identity, Tone, Boundaries, with example bullets in each.

Try it now

In Google AI Studio, build a persona for a "spicy roast comedian". Send 3 user messages. Note how the persona overrides natural model neutrality.

Hands-on lab

Write 3 distinct system prompts for the same task (summarize tech news), each with a different persona (analyst, comedian, kid-friendly explainer). Compare outputs.

Try it now

What happens if your system prompt conflicts with the user's request?

Common mistakes

1-line system prompts ("You are a helpful assistant.")
Persona-only system prompts with no constraints
Putting persona in every user message instead of once in system

Debugging tip

If your assistant breaks persona mid-conversation, your system prompt is probably too short or too vague. Add explicit rules.

Challenge

Convert any product page's tone of voice guide into a system prompt. Verify the model follows it across 5 turns.

Where this shows up

Branded chat assistants
Customer-facing AI features with strict tone
Internal coding copilots with org-specific rules

From the field

In production, system prompts are version-controlled and reviewed like code. They are also a hot reload point: change one line, instantly change product behavior.

Recap

The system prompt is your product's voice and rulebook. Invest in it. It is the highest-leverage 200 tokens you will ever write.

Quick recall

3 prompts · think before you flip

Prompt 1 of 3

What should a strong system prompt include?

Quiz time

1 question · tap an answer to check it

1. The system message should typically be