Prompt Basics for Beginners — A Simple First Guide

The word "prompt" can sound technical, but it's really just a single request message you send to Claude. Like typing words into a search box, with Claude you make a request in sentences. And the same task can give very different results depending on how you ask. This article explains, in the simplest terms, how to write good requests (prompts) for first-time Claude users.

What is a prompt?

A prompt is simply "what you tell Claude to do." For example, typing "make this email more polite" — that one line is a prompt. It's not a hard skill; just ask the way you'd ask a person. Unlike a person, though, Claude doesn't know your situation in advance, so the more relevant information you include, the better it can help.

The key principle: be clear and specific

The one thing the official guide stresses most is "be clear and specific." Vague wording is the leading cause of poor results. Claude tries to follow what's written rather than guess your mind. So writing exactly and specifically what you want is the key.

For example, instead of "summarize this," write "summarize this document in 3 short sentences." Better than "write it better" is "write it as a 5-item list, each item under 15 words."

5 things worth including in a good prompt

You don't need all of them — pick what you need. Keeping these five in mind noticeably improves results.

1. What to do (task) — be clear about the job. "Summarize this," "find the bug in this code," "draft an email."
2. Background & reason (context) — telling Claude why and in what situation helps it match tone and level. "This is for a presentation," "I'll explain it to a child." The official guide also notes that giving the reason/motivation behind an instruction helps the latest models follow it better.
3. What shape (format) — specify the output form: "as a table," "in 3 sentences," "as a list," "in JSON."
4. Show an example — showing one sample of the result you want greatly improves accuracy. One good example beats many adjectives.
5. What not to do (constraints) — set boundaries like "don't use jargon" or "don't guess; if unsure, say so." In particular, "if unsure, say so" helps reduce wrong information.

If it's your first time, follow this order

Don't strain to write the perfect prompt in one shot. Just send it, look at the result, and rephrase if it's lacking — repeat a few times. This is called "refining" your prompt.

1. Set the goal — think of what you want in one sentence.
2. Write specifically — pick what you need from the five above and state length, format, etc.
3. Send and check — see whether the result matches your expectation.
4. Rephrase — ask for tweaks like "a bit shorter" or "add one more example."
5. Repeat — lightly repeat until you get what you want.

Examples you can copy right away

Here are examples you can adapt directly.

• Email: "Rewrite the email below to be polite and concise. Within 3 sentences, with an apologetic tone."
• Summary: "Summarize this in 3 sentences so a beginner understands. Replace jargon with plain words."
• Ideas: "Give me 5 weekend family outing ideas as a list. One line each, focused on low-budget options."
• Learning: "Explain what 'compound interest' is as if to a middle schooler, with an example."

It's fine to start short. If the result falls short, remember: "do it again, more specifically."

Summary

A prompt isn't a hard skill — it's "asking clearly." State (1) what, (2) in what situation, (3) in what shape you want, (4) show an example, and (5) set what not to do. To learn more, continue with 7 principles for writing great prompts and ready-to-use prompt templates on this site.

This article explains the public principles from the official Anthropic prompting guide (platform.claude.com/docs) in beginner-friendly terms. This site is not an official Anthropic site.