Prompt Engineering Basics (Five Habits That Work)

"Prompt engineering" sounds technical, but it’s really just learning to ask well. There’s no secret syntax and there are no magic words. People who get good results from AI give it clearer instructions, and five habits cover almost all of it. If you’re brand new to the tools, start with ChatGPT for beginners, then come back here.

1. 01

   State the task and the format you want

   Lead with exactly what you want and what shape it should take. "Summarise this in five bullet points," "Write three subject-line options," "Turn these notes into a short client email." A vague ask gets a vague answer. Naming the output (a list, a table, a paragraph, a number of options) removes most of the guesswork before the model starts.

2. 02

   Give it a role and the context

   Tell it who it is being for this task ("you are a careful proofreader," "act as a sceptical reviewer"), and paste in the material it needs to work from. The role sets the tone and the standard, and the context is the raw material. The model can’t guess either one, and supplying them is what turns a generic answer into one that fits your situation.

3. 03

   Show it one good example

   If you have a version you like (a past email in your voice, a report in your format), paste it in and say "match this style." One good example teaches the model more than a paragraph of instructions, because it shows instead of telling. It’s the most underused habit of the five, and it’s the one that gets results that sound like you instead of a machine.

4. 04

   Constrain length, tone and what to avoid

   Left alone, models pad. Set limits: "under 120 words," "plain English, no jargon," "do not use the word ‘leverage’," "Australian spelling." Telling it what to avoid is as useful as telling it what to do. Constraints aren’t fussiness. They’re how you get something you can use as it is, instead of something you have to trim and fix.

5. 05

   Iterate, then save the winners

   The first answer is a draft. Push back: "tighter," "warmer," "cut the intro," "that is too formal." When one lands, save it. The prompts that work for your recurring tasks become a small personal library, and reusing a proven prompt beats writing a fresh one every time. That library, shared across a team, is most of what "getting good at AI" actually means.

People also ask

Do I need to learn prompt engineering as a proper skill?

Not as a technical discipline. For everyday work, the five habits above cover most of what matters: be specific, give context and an example, set constraints and iterate. The deeper technical side matters mostly when you’re building AI into a production system, not when you’re drafting an email.

Why do I get generic answers from AI?

Usually because the model had to guess. It fills gaps with the most average, safe response it can, so a vague ask gets a vague result. Add the specifics (audience, purpose, length, tone, an example) and the answer stops being generic, because it now has something to work with.

Worth saying plainly. Prompt engineering isn’t a skill worth putting a whole team through a course for, and we wouldn’t sell you one. It’s five habits, and people pick them up in an afternoon of doing real work. If somebody is quoting you for a prompt-engineering programme, it’s fair to ask what it covers beyond this page.