IntegrAuth Academy
Identity, security and practical AI — free, from zero. Byte-sized lessons, real diagrams, hands-on labs, zero fluff. Two programs, each with its own exam and certificate.
English is hard? Your browser can translate this page into Tamil, Telugu, Kannada, Malayalam or Hindi. Tech words stay in English so you learn the real names.
How?
- Chrome on phone: ⋮ menu → Translate
- Chrome on computer: right-click → Translate to …
- Edge: the translate icon in the address bar
Prompts that work
Priya pastes 40 customer comments into an AI and types "summarize this". She gets a cheerful sales text with a made-up number. Your goal: write a clear brief, and know what hidden rules can and cannot do.
🧪 Interactive lab — enable JavaScript to play with this one.
- A prompt is a brief. Say the goal, who it is for, and the format you want.
- Show an example or two. The model copies their pattern.
- Tell it to use only your material. Let it say "I'm not sure."
- Apps set hidden rules before you type. They steer well, but they are not a lock.
Who is talking
A chat is a list of messages. Each one has a label, called a role, that says who wrote it.
The app builder writes standing rules first. You do not see them. This is the system prompt. What you type is the user prompt. The model's own replies are the assistant turns.
Write a brief, not one word
A brief is a short, clear job description. Tell a tailor "stitch a shirt" and you get a guess. Give the size, cloth and date, and you get your shirt. You met its parts in Everyday wins with AI. The model knows nothing about your situation, so it guesses. Tell it your goal and why. Say who will read it. Add limits, like length. Say the exact format you want.
Show an example
Instructions tell. Examples show. You can add a few examples of input and good output. This is few-shot prompting. Three to five is a common start. Make them differ. The model copies every pattern, even ones you did not mean.
Now write hidden rules for a help bot.
🧪 Interactive lab — enable JavaScript to play with this one.
Go deeper: roles are labels, not walls
The model's earlier replies are sent back in each turn. That is how it "remembers" the chat. Your custom instructions, or project instructions, are your own part of the system prompt. With an API, you write all three roles yourself (Using AI through an API).
The model reads every role as one long stream of tokens. Models are trained to give system rules extra weight. But roles are labels on text, not walls. Users can often get a model to show its system prompt.
Go deeper: keep rules and material apart
Keep your instructions, your examples and your material clearly apart. Label each part. Or wrap each one in simple tags, such as <instructions>, <example> and <feedback>. With long documents, a common tip is to put the documents first and your question at the end.
Tags help the model tell data from instructions. But text inside a document can still change what the model does. No wording makes it safe. Real limits belong outside the model. Learn more in Prompt injection.
Go deeper: roles, formats and steps
- 🎭 Give it a role. "You are an experienced editor" changes its words, tone and focus. A role does not add knowledge the model lacks.
- 📋 Ask for a format. Ask for bullets, a table or a fixed template. Code can read structured output, such as JSON. A clear format is also easier to check.
- 🪜 Break it down. One prompt that does four jobs does each job worse. Split a big job into steps. Feed each result into the next. This is called prompt chaining.
- 🧠 Let it think first. Ask it to work through the problem before it answers. For example: list the themes, then count them. Reasoning models do this on their own. See Choosing a model.
Go deeper: fewer made-up answers
A model is built to give a smooth answer. If your prompt suggests there must be an answer, it may make one up. See When AI makes things up.
Three short lines help a lot:
- "Use only the material provided."
- "If the answer is not there, say you don't know."
- "Quote the sentence you used."
Asking it to list what it assumed helps too. It can still be wrong. But now you can see where it is unsure, and check.
Priya's better brief said who the summary was for. It asked for themes, counts and one real quote each. It said to use only these comments. The new answer showed that export problems were a quarter of all complaints.
A better prompt is the cheapest fix. It costs nothing and works with any model. Fix the brief before you pay for more. See Prompt, RAG or fine-tune?
To practice more, try Anthropic's free interactive prompt engineering tutorial. Or read the community Prompt Engineering Guide. Both teach skills that work with other models too.
Never put a secret in a system prompt. Users can often get the model to reveal it.
Pick a real task. Ask any AI twice: first with one line, then with a full brief. Compare the two answers.