Guide

Claude Docs and Claude Slides: how to get a good doc or deck on the first try

Published 4 October 2026

A laptop on a desk showing a simple document with a heading and a short table, next to a notebook and a cup of coffee

Short answerAsk Claude for a doc or a deck the same way you'd brief a colleague: say the goal, the audience, what to include, and the format you want it in. Claude Docs and Claude Slides then give you an editable file instead of a wall of chat text, which you can refine with more chat, inline comments, or by editing it directly.

Anthropic has been changing how Claude handles everyday work. Claude Cowork is being folded back into ordinary chat, and alongside that change, Anthropic launched two new beta features: Claude Docs and Claude Slides. Instead of pasting a long chat reply into Word or PowerPoint yourself, you can now ask Claude to hand you a document or a deck you edit directly.

This guide covers what each one does, who has access, and how to write a prompt that gets you a usable first draft instead of three rounds of back-and-forth.

What Claude Docs and Claude Slides actually are

Claude Docs is a rich-text document saved to your Claude account. It supports headings, tables and more than one tab, like sections in a notebook. Every doc lands in your Artifacts tab, so you can find it again from any conversation, and you can export it to Word, PDF, Markdown or Google Docs.

Claude Slides is Anthropic's presentation tool, part of the wider Claude Design beta. It builds a deck from your notes, a report, or the conversation you're already having, and you can export the result as PowerPoint or PDF, or present it straight from Claude.

Both are in beta and currently on Pro, Max and Team plans by default. Enterprise admins have to turn them on in Organization settings. According to Anthropic's support pages, Claude Docs doesn't yet have version history, so keep a copy of anything you can't afford to lose while the beta settles in.

How to start one

You don't need a special command for most of this, though a few shortcuts help:

Just ask. "Turn the plan we just worked through into a product spec" is enough to start a doc from an existing chat.
Use the Output menu. In the message box, choose Output > Design to start a deck or visual document from scratch.
Start from a template. The Artifacts tab has ready-made templates for both docs and slides.
Claude Code users can type /design to start a Design project without leaving the terminal.

Writing a prompt that gets a good first draft

A doc or deck prompt works best when it covers four things: the goal, the audience, what to include, and the format. This is the same 5-part prompt structure that works for any Claude prompt, just aimed at a finished file instead of a chat reply.

A weak prompt:

prompt

Make me a one-pager about our Q3 results.

A stronger one:

prompt — 1 blank

Create a doc: a one-page summary of our Q3 results for the leadership team.
Audience: executives who will skim it in under two minutes.
Include: total revenue, the three biggest changes from Q2, and one risk to watch.
Format: a short headline, 5 bullet points, then a one-line "Risk" section.
Source: use only the figures in the table below. If something isn't in it, write "not in the data".

<sales_table>
[PASTE YOUR TABLE HERE]
</sales_table>

For a deck, add the shape of the story as well as the content:

prompt — 3 blanks

Create a slide deck: a 6-slide pitch for [WHAT YOU'RE PITCHING].
Audience: [WHO WILL SEE IT, e.g. a bank, a landlord, an investor].
Slides: problem, our approach, who it's for, how it makes money, the ask, next steps.
Tone: confident but plain, no jargon.
Source material: [PASTE YOUR NOTES, A REPORT, OR A SUMMARY OF THE CONVERSATION HERE]

The one-page project plan prompt and the executive summary prompt both work well as a starting brief you paste in, then ask Claude to turn into a doc. If your deck needs a comparison slide, the competitor comparison prompt gives you the structure to build it from, and a SWOT slide or a roadmap slide are common additions worth asking for by name.

Refining the draft

Three ways to fix a doc or deck once it exists, and each suits a different kind of change:

Chat for structural changes. "Move the risk section above the bullets" or "cut this to 4 slides" is easiest to say in plain language.
Inline comments for small fixes. Comment directly on the part that's wrong, and mention @Claude in the comment to have it fix just that piece.
Direct editing for anything visual. You can click into the canvas and change text, move a block, or adjust layout by hand, the same as you would in Word or PowerPoint.

If you're sharing a doc with other people, remember that whoever owns it decides who can view or edit it, and on Pro and Max plans you can share a doc with anyone through a link. Team and Enterprise accounts can't share outside the organisation.

Common mistakes

Describing the topic but not the audience. "A report on sales" leaves Claude guessing how formal or detailed to make it. Say who's reading it.

Asking for a deck with no slide count or structure. Without a shape to follow, you'll get whatever length Claude picks, which may not match the time you have to present it in.

Forgetting the source material. Claude Docs and Slides can draw on your connected files and past conversation, but a pasted table or report still gets more accurate numbers than a general request.

Treating the first draft as final. Ask for one structural change at a time rather than rewriting your prompt from scratch. It's faster, and it's easier to tell what actually improved.

Where to go from here

If you're switching from the separate Cowork experience, see our guide to prompting the new unified Claude for how check-ins and task delegation work now. More ready-made work prompts are free in the productivity prompts collection, and the prompt builder can turn a rough idea into a structured brief for a doc or a deck in a few questions.

Quick checklist

Say the goal, the audience, what to include, and the format, before you ask for the doc or deck.
For a deck, name the number of slides and what each one should cover.
Paste your source material instead of describing it from memory.
Use chat for structure, comments for small fixes, and direct editing for layout.
Keep your own copy while the beta has no version history.