Artifacts, Claude Docs, Slides and Design: create, iterate and share

0:00 Artifacts

What if the output of your AI conversation was not a wall of text, but the actual thing you need? The editable brief. The board deck. The landing page mock up. The calculator your sales team uses every day. That is what Claude's Artifacts are for, and in this lecture you will learn to create, iterate and share them like a pro.

0:27 Why Artifacts matter

Why do Artifacts matter? Because in most jobs, the output is the work. A brief, a deck, a calculator. When the result arrives as chat text, you still spend time copying, formatting and fixing it somewhere else. An Artifact arrives as the thing itself, ready to edit, download or share. It is the difference between a colleague telling you what the slides should say, and a colleague handing you the slides. And with in place editing, you keep control over every sentence.

1:03 What changed in September 2026

When Claude produces something substantial, it opens as an Artifact beside the chat. In September twenty twenty six this expanded into four families. Claude Docs, for documents you write together. Claude Slides, for presentations you can export to PowerPoint or PDF or present straight from Claude. Claude Design, for visual mock ups and prototypes with on canvas editing and the ability to import your design system. And interactive artifacts, small tools like calculators, checklists and quizzes built from code. Everything lives at one shareable link, which you can open on your phone.

1:43 When to ask for one

Ask for an Artifact when the output is something you will reuse, edit, present or share. A template, a deck, a checklist, a one page brief, a tool. Quick answers and explanations belong in chat. Be explicit. Create this as a Claude Doc I can edit. Build a ten slide deck from these notes with speaker notes. Make an interactive calculator as an artifact.

2:11 Edit in place

One of the best recent improvements is in place editing. Instead of asking Claude to regenerate an entire document, highlight the part you want changed and type the change. Make this friendlier. Add the delivery date. Swap these two bullets. Everything else stays exactly as it was, which means you stop losing good work to a full rewrite.

2:36 Mini-tools without code

Non engineers can build real internal tools by describing them. Picture a creator campaign cost calculator. You list the inputs, number of creators, fee per creator, usage rights percentage, agency margin and currency. You list the outputs and the rules, handle zero and blank inputs, format currency, show a note saying estimates only. Then iterate one change at a time, and describe bugs precisely. When creators is zero, the total shows N a N, show zero instead and keep everything else unchanged. Test normal values, zero, huge numbers and blanks.

3:15 Decks that do not look AI-made

For decks, give Claude the story, not just topics. Audience, goal, and the narrative arc, problem, evidence, pilot design, costs and risks, decision needed. Set rules like thirty words maximum per slide, one chart where data exists, and speaker notes. Supply your brand template. Then ask for a sceptic slide listing the three hardest questions your audience will ask. That one addition makes you look far more prepared.

3:45 Simple example

A simple example first. Ask, create an interactive packing checklist for a two day trade show in Dubai, grouped by category, with checkboxes. You get a working checklist you can tick off on your phone. Notice something is wrong? Fifty brochures should be one hundred and fifty. Highlight that item, type the change, and only that line updates. Share the link with a colleague and they can use it too. That is an Artifact in thirty seconds. The rest of this lecture scales that idea up to decks, designs and real business tools.

4:25 Worked example: a franchise pilot

An operations lead at a coffee chain in Saudi Arabia pastes her notes and a CSV of missed orders. Claude builds a nine slide deck with a chart from the data, speaker notes and a risks slide. She edits two slides in place, asks Claude Design for a mobile mock up of the WhatsApp ordering flow for slide five, exports to PowerPoint for the board pack, and checks every figure against the CSV before it goes anywhere. The AI did the assembly. She did the judgement. Two weeks later the board asked for the same deck with updated numbers. Because it lived as an Artifact with version history, she pasted the new CSV, asked Claude to refresh only the chart and the figures on slides three and seven, and checked those numbers again. The rest of the deck, which the board already liked, stayed exactly the same.

5:29 Sharing safely

Before you share, check who can open the link and whether your organisation allows it, since admins on Team and Enterprise plans can restrict sharing. Never embed secrets like API keys or passwords, and leave out personal data you do not need. Label drafts and estimates clearly. And treat anything published like a public web page, accurate, compliant and owned by a named person.

5:57 Try this now

Try this now. Think of one small calculation or checklist you repeat every week, a quote calculator, a content calendar checker, a meeting prep list. Describe it to Claude as an interactive artifact with clear inputs, outputs and rules. Test it with normal values, zero, a very large number and a blank. Fix any bug with a precise description. Then take the rough notes from your last meeting and ask for a six slide deck with speaker notes. Edit one slide in place, check every number, and export it. You now own two reusable Artifacts.

6:38 Watch me do it, part 1

Let me build the creator campaign calculator. I paste the specification. Inputs, number of creators, fee per creator, posts each, usage rights percentage, agency margin and currency. Outputs, subtotal, rights fee, margin, total and cost per post. Rules, handle zero and blank inputs, format currency, and show estimates only. The calculator appears beside the chat. I test it. Five creators at two thousand dirhams, fine. Now zero creators, and the cost per post shows N a N. So I type exactly what is wrong. When creators is zero, cost per post shows N a N, show zero instead and keep everything else unchanged. It updates, and I retest zero and a blank. Both behave.

7:28 Watch me do it, part 2

Next, the franchise deck. I paste my notes and the missed orders CSV with the narrative prompt. Audience, franchise owners in Jeddah and Riyadh. Goal, approve a pilot in five stores. Thirty words per slide maximum, one chart where data exists, speaker notes, Arabic titles under English titles. Nine slides appear. Slide four's title is too long, so I highlight it and type, shorten to six words. Only that title changes. I ask for a sceptic slide with the three hardest questions. Then I export to PowerPoint, and before sending I check every number on the chart slide against the CSV. One total was rounded, so I correct it and export again.

8:17 Recap and next step

Recap. Artifacts turn conversations into real deliverables, Docs, Slides, Designs and interactive tools. Ask for them when you will reuse, edit, present or share. Edit in place, iterate one change at a time, give decks a narrative, check every number, and share with care. Your next step: build one interactive artifact you will use weekly, and one real deck from your own notes, then verify every figure before you present it.