What a Claude Artifact is, and when to ask for one

Example result.

Client workshop: Harbour Street office, Tuesday 17 November, 10:00–12:30
Host: Dana Okafor · Attendees: 14 confirmed
Room: Meeting room 3, booked
Lunch: ordered for 12 (two attendees still to confirm dietary needs)
Open: visitor parking not confirmed

An Artifact is something Claude makes that you’d put in front of someone: a document, deck, design, dashboard or small interactive tool. It opens in its own window beside the chat, so the result stays in one place while you revise it.

1. Decide whether the job needs an Artifact

Ask for an Artifact when you’ll edit the result, reuse it outside the chat or hand it to someone. Keep a quick answer in the chat.

Claude often makes an Artifact on its own for anything long and self-contained. Saying “as an Artifact” removes the guesswork. You can also select Output in the message box and choose a template such as a doc or slides.

Why this works: an Artifact earns its place when the result has a life after the chat. If you won’t come back to it, a chat answer is quicker.

What you should see: a clear yes or no for your job, and the one line you’ll type.

2. Turn the setting on and ask for the brief

If Artifacts never appear, open Settings › Capabilities and turn on Cloud code execution and file creation. On a Team or Enterprise plan this sits in Organization settings › Capabilities, so an owner may need to switch it on.

Then paste your notes and ask:

Turn these notes into a one-page event brief as an Artifact for [reader]. Use only the facts in the notes. Keep anything marked unconfirmed as an open question, and add a short "Still to confirm" section at the end. Don't add times, names or numbers that aren't in the notes.

Notes:
[your notes]

[reader] is who will use the brief, such as “the client’s project lead”. [your notes] is everything you know so far, including the gaps.

Why this works: “only the facts in the notes” and a “Still to confirm” section stop a tidy document from filling gaps with plausible guesses.

What you should see: the brief opens in a window beside the conversation. It’s also saved in the Artifacts tab in the sidebar, so you can find it later. On iOS and Android, open it from the Artifacts tab.

3. Check the brief against your notes

Read the Artifact, not Claude’s chat summary of it. Tick off each fact in your notes: date, time, place, names, numbers. Then read the brief for anything that isn’t in your notes. A confident “parking available on site” in a brief whose notes said “not confirmed” is the kind of thing a reader will act on.

Why this works: the brief will be read without the chat beside it, so it has to be right on its own.

What you should see: every note accounted for, every open question still open.

4. Revise it with one focused change

Ask for one change at a time and name what must stay the same.

In the brief Artifact, change only [section]: [the change]. Leave every other section word for word as it is. Then list exactly what you changed.

[section] is the heading you want edited, and [the change] is the new fact or wording. In a doc, you can also highlight text and choose Edit with Claude.

When the brief is ready, use Export to download it as Word, PDF or Markdown, or send it to Google Docs. To try a different direction without losing this one, edit an earlier message: Claude starts a new branch of the chat with its own Artifact, and your previous work stays where it was.

Why this works: a narrow request gives Claude less reason to rewrite the whole page, and the change list tells you where to look.

What you should see: one section changed, and a change list that matches what you can see.

Check the result

• Every fact in your notes appears in the brief, with the same figure.
• Nothing in the brief is missing from your notes.
• Sections you didn’t ask to change are word for word the same.
• Open questions are still open.

The usual failure: you ask for one small change and Claude regenerates the whole brief. The new version reads better, and somewhere in it an open question has quietly become a fact, or a number has drifted. Compare the “Still to confirm” section and every figure with the previous version.

The revision changed [what changed] although I only asked you to edit [section]. Restore it to the previous wording, keep my requested change, and confirm which sections now differ from the previous version.

[what changed] is the line that moved without being asked; [section] is the one you meant to edit.

Fictional example. Dana’s notes for a client workshop:

Tues 17 Nov, Harbour Street office, 10:00–12:30
Dana Okafor hosting. 14 confirmed.
Meeting room 3 booked.
Lunch ordered for 12; 2 people still to send dietary needs.
Visitor parking: asked facilities, no answer yet.

The first brief matched the notes. Dana then asked: “Add a 15-minute coffee break at 11:00.” The revised Artifact had the break, and also this:

Getting here: Visitor parking is available on site. Lunch is provided for all attendees.

• The failure. Two facts moved without being asked. Parking went from “no answer yet” to available, and “lunch for 12” became “all attendees” (14). The chat reply said only “Added the coffee break.”
• The repair. Dana used the repair prompt with “the parking and lunch lines” and “the agenda”. Claude restored “Visitor parking: not yet confirmed” and “Lunch ordered for 12; two still to confirm”, kept the break and reported that only the agenda had changed.
• Why the check caught it. Comparing every figure with the notes takes a minute, and 12 versus 14 is easy to spot once you look for it.

Task kit for this job: Download (ZIP) · Reusable instructions

Go deeper

Sources

• Claude Help Center: What are artifacts and how do I use them?