At most one email a week. Unfollow anytime with one click.
Transcript
The full narration of this video. The current sentence is highlighted while the video plays; click any sentence to jump there.
Show transcript
Introduction
Hi, and welcome to the Artifacts session. In this session, Claude's work is no longer just text in a chat; it becomes something you can see, use, and share. In the first episode of this session we get to know Artifacts: what they are, when Claude creates them, their types, the parts of the panel, and the learning map to the end of the session.
Step 1: What is an Artifact?
An Artifact is a piece of Claude's work that appears in its own panel, to the right of the chat. The word artifact itself means an object someone has made. The split is clear: the chat on the left is for discussion, and the panel on the right is for results you can use right away. The result doesn't get buried among long chat replies. Let's look at an example. Laras asks for a Sunset Coffee menu to print and stick on the cashier counter, complete with prices and opening hours. Claude replies briefly in the chat, while the result appears in the right panel: a title, a menu table with sizes and prices, then shipping info and opening hours. Notice that the chat reply stays short. The main result isn't mixed in with the conversation, so it's easy to read, copy, or print. At the top of the panel are the Artifact's title, a version label, v one, and two tabs: Preview and Code. We'll cover these parts in step four. What can we do with an Artifact? First, view it. The result is shown neatly, not mixed in with the chat text. Second, copy or download it, then use it in other documents, print it, or put it on a website. Third, ask for changes. We don't edit it ourselves; we just write the change we want in the chat, and Claude updates the panel. Fourth, share it with coworkers or customers. Sharing needs to be used carefully, and we'll cover it fully at the end of the session.
Step 2: When does Claude create an Artifact?
So when does Claude create an Artifact? There are four signs. First, the result is long and self-contained, meaning it can be read without looking at the earlier conversation. Second, the result will be reused or edited, like a menu, an SOP, a template, or a report. Third, the result is better seen than read, such as a web page, a chart, or a diagram. Fourth, the result can be clicked or filled in, like a calculator, a quiz, or an interactive checklist. In short, if you plan to save, print, or share the result, there's a good chance it will become an Artifact. The difference is easy to remember. A question about what a term means is fine in the chat. A menu to print becomes an Artifact. An answer of one or two paragraphs stays in the chat. A result that's a page or longer usually goes into the Artifact panel. Things you read once stay in the chat, while things you'll reuse, edit, or share are better as Artifacts. If an Artifact doesn't appear when you need one, just ask for it directly. Notice that Laras adds the sentence: make it an Artifact so I can print it. Claude understands the request and creates an Artifact. If it still doesn't appear, check whether the Artifacts feature is turned on in your Claude app settings. Menu names may differ slightly because Claude is updated often.
Step 3: Types of Artifacts
Artifacts come in many forms. The first and most common are documents and checklists, such as SOPs, letters, menus, and prep lists. Second, tables and charts, such as a monthly sales recap or a comparison of supplier prices. Third, calculators and small tools, like an order total, cost of goods, or discount calculator. Fourth, web pages, such as a business profile, a promo page, or an event invitation. Fifth, quizzes and interactive apps, like practice questions for students or a simple survey. We'll practice all five types one by one throughout the session, with examples from Sunset Coffee, Maju Bersama Co., and Cerdas Tutoring. An example of the tables and charts type comes from Dewi. She pastes six months of sales data and asks for a bar chart and a number summary for tomorrow's meeting. The right panel shows three number cards: the six-month total, the highest month, and the monthly average, followed by a bar chart by month. Dewi still checks the total against the original data before the meeting. An example of the interactive type comes from Mr. Hendra at Cerdas Tutoring. He asks for a five-question fractions quiz with a check answer button. Claude creates a quiz you can click right in the right panel. The question uses an everyday story, there are answer choices, and a button to check. Mr. Hendra didn't write a single line of code. These three examples, the menu, the chart, and the quiz, were all created from requests in everyday language. The only difference is what we asked for.
Step 4: Parts of the Artifact panel
Let's go back to Laras's menu to learn the parts of the panel. The opening conversation is the same. Laras then asks for a small change: add a note that the gift hamper comes in a sugar-free version. Claude updates the Artifact. Notice the label at the top of the panel now says v two. Every change creates a new version, and the previous version is still saved. Now click the Code tab. This is what's behind the view we just saw: the menu, prices, shipping, and opening hours, written in a programming language. We don't need to understand it; Claude writes and maintains it. The Code tab is useful if one day you want to copy the result somewhere else, such as a website. For everyday use, we just work in the Preview tab. Back to Preview. Around the panel there are usually also buttons to copy, download, or share the result. Their position and names may differ in your app. Let's sum up. The first part is the title, the name of the work, which makes it easy to find again. Second, the version. This label goes up with every change, so we can go back to an older version if needed. Third, Preview: the ready-to-use view of the result. This is where we work most often. Fourth, Code: what's behind the view. It's enough to know where it is; Claude takes care of it.
Step 5: Safety rules and session map
Before creating your own Artifacts, remember four safety rules. First, check numbers, names, and facts before using them. A tidy Artifact can still contain mistakes. Second, for interactive Artifacts like calculators and quizzes, try every button and field. Make sure the calculations are right. Third, keep copies of important results on your computer or drive. Fourth, don't put customers' personal data in an Artifact you'll share. We'll cover how to share safely at the end of this session. Here's the map of the Artifacts session. In the next episode we create documents and checklists, the simplest and most frequently used Artifacts. After that, tables and calculators for everyday business math, such as cost of goods and order totals. Then a one-page website without coding, such as a Sunset Coffee promo page. Finally, revising and sharing Artifacts: managing versions and sharing results safely. By the end of the session, you'll have at least one real Artifact you can share, whether for your business, office, or class.
Done!
We've gotten to know Artifacts: work shown in the right panel, when Claude creates them, the five types, and the title, version, Preview, and Code parts. In the next episode we create our very own first Artifact: an SOP document and a checklist you can tick, for business and office alike. See you there!
Practice exercises
Try these on your own after watching to lock in what you learned.
Ask Claude to create a short document for your business and see whether it appears as an Artifact
Open the Code tab of that Artifact, then go back to Preview
Write down three routine pieces of work that would make good Artifacts
Ask the class material
Type a question or keyword; we find the part of this episode that explains it and jump the video there.
My notes
Notes are saved with the current video time and are only visible to you.
Questions & answers
Stuck on a step? Ask here; the instructor and other learners can answer.
No questions yet.
Your instructor
Cerdas Inovasi Digital Team
Software developers, BIM & 3D engineers, and AI practitioners
53 video classes1,286 episodes
We build software, BIM models, games and AI automations for clients every day, and turn that hands-on work into step-by-step classes: every step is shown on screen and comes with a PDF guide you can keep.
