Write a prompt like a one-paragraph brief

It is 9:12 on a Tuesday and you have twenty minutes before a call. You told your team you would come with a draft of the investor update. You open Claude.ai, see the clean text box at the bottom of the screen, and your hands hover over the keyboard. You know Claude can help. You just do not know what to type first.

This lesson is the answer to that hesitation. By the end of it you will know how to open a conversation, what to put in your first prompt, how to add context with files, and how to steer Claude's response with follow-up messages instead of starting over.

1. Open Claude and orient yourself

Go to claude.ai and sign in. The interface is deliberately sparse: a sidebar on the left, a text box at the bottom, and a big empty space in the middle where the conversation will appear.

A quick tour of what lives in the sidebar:

• New chat — starts a fresh conversation with no memory of previous chats.
• Projects — persistent workspaces with their own files, custom instructions, and context. You will meet these properly in Module 2.
• Artifacts — standalone outputs (drafts, documents, small apps) that Claude creates in a side pane so you can edit them without drowning the chat. Also coming in Module 2.

For now, stay on a new chat. That is where you write your first prompt.

2. Write a prompt like you would brief a coworker

Every interaction with Claude starts with a prompt. The best way to think about a prompt is not as a magic incantation but as a brief — the kind of context you would give a new colleague before handing them a task. Naturally, concisely, conversationally.

A good prompt has three parts. You will use them together on almost every real task.

Set the stage. Who are you, what is the work for, and what context does Claude need before it can help? "I am the marketing lead at an indie streaming startup preparing an investor pitch deck."

Define the task. What concrete action do you want Claude to take? Write, analyse, outline, draft, compare, explain. "Research the current state of the independent film streaming market and identify key trends, competitor positioning, and growth opportunities."

Specify the rules. What does the output need to look like? Tone, format, length, citations, examples. "Use current web research with citations. Structure it as a professional report of up to 5 pages with an executive summary, market analysis, competitive landscape, and growth opportunities."

Put those three pieces together and you get something like this:

I'm the marketing lead at an indie streaming startup and we're preparing
an investor pitch deck for Series A investors. Research the current state
of the independent film streaming market and identify key trends, competitor
positioning, and growth opportunities. Use current web research with
citations and structure it as a professional report of up to 5 pages, with
an executive summary, market analysis, competitive landscape, and growth
opportunities.

Notice how specific it is. Role, audience, task, format, length, and the standards the output has to meet — all in one paragraph. That is your default prompt shape. Use it as a mental checklist any time the blank chat box gives you pause.

3. Add the context Claude cannot guess

Your prompt says what you want. File uploads and connectors tell Claude about your world. They are the shortcut that turns a good generic response into a usable one.

Claude can read both the text and the visual elements of many common file types — PDF, DOCX, CSV, TXT, and images like PNG and JPEG. Click the attachment button next to the compose box, pick a file, and it appears in your message as an attachment. Some useful moves:

• Upload a document and ask Claude to summarise the key points.
• Share an image or chart and ask Claude to describe or analyse what it sees.
• Attach a spreadsheet and ask Claude to spot trends.
• Paste code and ask Claude to explain how it works or find a bug.

Pro tip. For things you want Claude to consider in every conversation — your role, your company, your writing style — set a preference in Settings → General → What personal preferences should Claude consider? These apply to every new chat automatically, so you stop re-explaining who you are every morning.

4. Iterate — do not start over

The first response is almost never the finished product. That is a feature, not a failure. Treat your first prompt as the opening of a dialogue, not a one-shot request.

When the response is close but not quite right, you have three moves:

1. Ask a follow-up. "Can you expand on the second point?" or "That is helpful, but can you make it more concise?"
2. Give specific feedback. "This is good, but the tone is too formal. Make it more conversational, and cut the first paragraph — it is setup I already know."
3. Redirect. "Actually, I was asking about enterprise customers, not prosumers. Let me clarify." If the conversation has drifted too far, start a fresh chat with a cleaner prompt — that is often faster than fighting your way back.

Pro tip. You can click the pencil icon on any of your own messages to edit and resubmit it — useful when you want to refine your original request rather than append a new one.

5. Let Claude learn you

Two features make every future conversation better, and both are worth turning on early.

Memory automatically saves key context from your conversations — your role, your preferences, past decisions, working style — so you stop repeating yourself. Tell Claude once that you work in marketing at a B2B company, and it will remember. You can review, edit, or delete anything Claude remembers from Settings, and Memory syncs across devices.

Styles let you customise how Claude communicates. Pick a preset — concise, formal, explanatory — or describe your own. Once set, the style applies across all conversations.

These are the quiet multipliers. Small setup now, noticeable payoff every day.

Put it into practice

Before you move on, open Claude and run one prompt using the three-part shape. Pick something real — an email you have been avoiding, a summary you need, an analysis you do not want to start from scratch. Set the stage, define the task, specify the rules, and see what comes back. Then iterate once. Not to get the perfect answer — just to feel what it is like to steer a response instead of accepting the first draft.