Prompt
Also known as: prompting · prompt engineering
A prompt is everything the model sees in one turn: your question, the conversation before it, any system instructions, and any documents you attached. In practice, “prompt” = the full input.
Most systems have at least two layers:
- System prompt — invisible instructions set by the app (“you are a helpful assistant, always answer in French…”). You don’t write this; the product does.
- Your prompt — the message you type. Plus whatever context the app re-injects (history, files, search results).
Prompting is less “magic words” and more communication. What actually works:
- Be concrete. “Fix this function” → “This function returns
nullon empty input; make it return[]instead.” - Show examples. One good example beats three paragraphs of description.
- Give it the material. If the answer needs data, put the data in the prompt — the model can’t mind-read.
- Iterate. Treat the first answer as a draft, then refine the prompt.
Caution: a prompt that *describes* what you want is fine; a prompt that *contains* untrusted text (web pages, emails, logs) is a different animal — that's where [prompt injection](/glossary/prompt-injection/) lives.