How to Write Better AI Prompts: A Beginner's Guide

The everyday problem

You ask an assistant to “make this better” and get a smooth response that misses the point. The problem may be an underspecified brief. A prompt works better when the assistant can tell what result you want and what information it must preserve.

Which tool to use, and why

Use ChatGPT or Gemini. The exercise is based on writing a clearer brief, so it transfers between text assistants without requiring a particular model or paid feature.

A quick way to improve an existing prompt

Underline the action, circle the facts, and list the acceptance checks. If you cannot find one of those three things, add it before making the prompt longer. Then ask the assistant to return only the requested output, or to separate a draft from notes.

When the first result fails, diagnose the failure. A wrong tone needs a tone correction; a fabricated deadline needs a no-invention rule and a missing-information policy. Rewriting the entire prompt can make the useful parts harder to identify.

Step by step

Name the task with a verb: summarize, compare, rewrite, classify, or plan. Choose one primary task first.
Supply only the context needed for that task. State the audience, purpose, and any facts that cannot change.
Add measurable constraints such as 120 words, three bullets, or a two-column table. Avoid vague instructions like “make it great.”
Specify what to do when information is missing: ask a question, mark it unknown, or leave a placeholder.
Review the result against your brief. Refine the one instruction that caused a mismatch, then try again.

A prompt you can copy

Replace every bracketed placeholder with your own non-sensitive information before you use this prompt.

Task: rewrite the note below for [audience]. Purpose: [desired action]. Keep these facts unchanged: [facts]. Tone: [tone]. Output: [format and length]. Do not invent deadlines or commitments. If an essential fact is missing, ask before drafting. Note: [text].

A worked example

Illustrative example: this input and output were written to explain the workflow. They are not a live product test, a user testimonial, or a promise of identical output.

Example input

Vague prompt: “Improve this.” Better brief: “Rewrite this reminder for a volunteer group in under 60 words. Keep Sunday at 10 a.m. and the library meeting room unchanged. Ask people to bring their own notebook.”

Example output

Reminder: our volunteer meeting is this Sunday at 10 a.m. in the library meeting room. Please bring your own notebook. Looking forward to seeing everyone there!

Check the result

A useful result meets both the content requirements and the format limit. Count the words if length matters. Check whether the assistant invented a purpose, attendee, or extra instruction.

Common mistakes to avoid

Adding a long fictional role while leaving the task unclear. The objective and constraints usually matter more.
Asking for private internal reasoning. Ask for a concise explanation, evidence, or an explicit checklist you can inspect.
Reusing a template without replacing bracketed placeholders.

Frequently asked questions

How long should my prompt be?

Long enough to remove important ambiguity. A short complete brief is often easier to use than a long contradictory one.

Should I provide an example?

Yes, when format or tone is hard to describe. Label examples clearly and explain which features to imitate.

Keep learning

Official documentation and availability

Product interfaces, plans, limits, and optional features can change. Check the current documentation for your own account. This guide’s original prompt and worked example do not depend on a particular model version.