IF YOU TAKE ONE THING AWAY

Tell the assistant the task, context, constraints, and format. Then judge the result and give specific feedback.

Brief it like a helpful colleague

A prompt is simply your instruction. You do not need a secret phrase or an elaborate role-play. The assistant needs enough information to understand what you are trying to achieve and what a good result would look like.

A useful pattern has four parts: task, context, constraints, and format. Not every request needs all four. A simple definition can be one sentence; a project plan needs more context. Add detail when it changes the result, not just to make the prompt longer.

Make the four parts concrete

Task: “Draft an invitation.” Context: “It is for neighbors attending a small community cleanup.” Constraints: “Friendly, under 100 words, and do not invent a time.” Format: “Give me an email subject and a short message.” These instructions are easy to follow and easy to evaluate.

If you know the tone you want, include a short example you wrote yourself. Examples can communicate style more clearly than a list of adjectives. Avoid pasting someone else’s private message just to demonstrate a tone.

TRY THIS PROMPT

Task: draft a friendly invitation to a neighborhood cleanup. Context: people may not know each other yet. Constraints: under 100 words; use [DATE], [TIME], and [MEETING POINT] as placeholders; no invented details. Format: one email subject and one short message.

Ask for clarification when details matter

If your request is ambiguous, ask the assistant to pose two or three questions first. This is useful for planning, recommendations, or a document with a specific audience. You can also ask it to list the assumptions it made.

For factual tasks, tell it which source material to use. “Summarize only the following text” is more constrained than “Tell me about this topic.” Still compare the answer with the source: even a source-bound summary can omit or distort a detail.

Separate your instructions from the material to work on. A line such as “Source text starts below” followed by the document makes your intent clearer. If the source contains instructions of its own, explicitly ask the assistant to treat them as quoted material rather than commands. This helps clarify the brief, but does not guarantee protection from misleading source content.

Edit the conversation, not just the prompt

After the first response, name the problem precisely. “Make this better” gives little direction. “Keep the friendly opening, remove the sales language, and shorten the last paragraph” is easier to act on.

When a conversation has become tangled, start fresh with your updated brief. Save prompts that work, but keep them short enough to adapt. A reusable template should help you think about the task, not lock you into a script.

Go to the source

Use these official resources to check product details and explore further. Features and policies can change.

One step taken. Keep your curiosity.

Back to all guides