On this pageA prompt is how you give the taskStart with three simple partsCompare a vague and clear requestGive examples when words are not enoughWhat if the answer is still poor?Try it: improve your own requestSources
DT

Written and reviewed by DeviceterraPractical guidance · Updated October 7, 2026

THE SHORT ANSWER

A prompt is the input you give an AI system. In chat, it usually includes your request and any details the model needs.

WATCH THE EXPLANATION

Jeff Su: Master the Perfect ChatGPT Prompt Formula

Jeff shows how task, background, examples, format, and tone affect a request. His demonstration uses cloud chat; the basic writing skills also apply to local text models. No prompt formula guarantees a correct answer.

Watch on YouTube or turn on captions ↗
THE FULL GUIDE

Here is what matters, why it matters and how to check it on your own setup.

01

A prompt is how you give the task

A prompt might be a question, an instruction, or text you want rewritten. In a picture-capable app, it can also include an image. Today, we will use text only.

Imagine asking a classmate, “Help me.” They need more information. “Help me write a short invitation for Saturday’s school fair” gives them a useful starting point. A model also benefits from a clear task.

You do not need special magic words. You need to say what you want, provide useful details, and check the result.

02

Start with three simple parts

Say the job: explain, list, rewrite, or compare. Add the facts the answer must use. Then say what the result should look like.

For example: “Write a notice for a shop. It is closed Friday and opens Saturday at 9 am. Use two friendly sentences. Do not add a reason for the closure.”

The final instruction matters because you did not supply a reason. A model may otherwise invent one.

Build a clear request
Build a clear requestJob: write a noticeFacts: dates + timeShape: two sentences

Put the job, relevant facts, and desired shape together. This is a helpful starting pattern, not a rule for every request.

03

Compare a vague and clear request

Vague: “Write about recycling.” That leaves the audience, purpose, and length unclear.

Clear: “Explain recycling to a 12-year-old. Use 120 words and one example about a plastic bottle. Explain that local collection rules can differ. Do not invent rules for my town.”

The clear version gives you things to check: audience, length, example, and honesty about missing information. A useful answer still needs your review.

04

Give examples when words are not enough

Suppose you want labels that look like “Milk: keep cool.” Show that example and ask for the same short format. The example helps explain the shape you want.

Use made-up examples while learning. Do not paste private customer data into an app until you understand where it runs and what it saves.

You can also ask for simple language or a calm tone. Telling the model to “act like an expert” changes the style of the request; it does not give the model a real qualification.

05

What if the answer is still poor?

Check the request first. Did you leave out a fact, ask several different jobs at once, or include conflicting instructions? Change one thing, then try again.

If a required fact is missing, provide a trusted source passage or ask the model to explain what information it needs. Asking it to sound more confident is not a way to make facts true.

Some tasks are beyond a model’s abilities. A better prompt cannot fix every weakness, and “think carefully” is not proof of a checked answer.

06

Try it: improve your own request

Write one harmless request in a single sentence. Now add the audience, facts, and desired format. Compare the two replies using the same model.

Mark which reply followed instructions, which facts need checking, and whether either invented a detail. Save the clearer request as a starting template, not as a guaranteed solution.

  • State one main job.
  • Supply relevant facts, not every detail you know.
  • Describe the result you want.
  • Check important claims before using the answer.
Quick check

A prompt is the request. The answer is the output. Clear instructions help, but they do not guarantee truth.

RESEARCH SOURCES

Official facts and real user evidence

Official documentation supports product and model facts. Community discussions show real setups, failures, and questions. A community result is supporting evidence, not a promise that another computer will perform the same way.

YOUR NEXT STEP

Watch a real test. Check what fits your computer.

See practical local AI tests from DeviceTerra, then use MamiLens to build a hardware-aware shortlist for your own setup.

This guide is educational. Model software, licenses, and hardware support can change. Check official sources before an important deployment.