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, we've reached the final episode of the Artifacts session. You can already create Artifacts; now we learn to polish and share them. In this episode we cover a focused revision pattern, how to prevent unrequested changes, managing versions, options for sharing Artifacts, and safety rules before sharing.
Step 1: A focused revision pattern
Every revision should follow four steps. First, look: read the whole Artifact calmly, not just at a glance. Second, mark the parts that need changing. Note it on paper or in your head: which part, and what you want it to become. Third, ask for one or two specific changes in a single message. Fourth, check the whole result, not just the part that changed. This fourth step is the one people skip most often, and we'll see why it matters in a moment. This pattern works for every type of Artifact: documents, calculators, and web pages. The more important the result, the more careful the checking step. Let's practice with the Sunset Coffee web page. The end of the year arrives, and Laras wants to add a promo section: a gift hamper plus one cold brew for one hundred ninety thousand, valid until December thirty-first. Version three appears. The promo section sits below the order button and stands out. At a glance, everything looks fine. But Laras does step four and reads the whole page. Look at the gift hamper card: its price changed to one hundred sixty thousand, when it should be one hundred fifty thousand. This is why the checking step must never be skipped. When revising, Claude sometimes changes other parts you didn't ask about. A small mistake like this can cost you if it's shared right away. Laras writes a specific correction: name the part that's wrong, the correct value, and one important sentence: don't change anything else. Version four fixes the hamper price back to one hundred fifty thousand, and everything else stays the same. Laras checks the whole page once more before moving on. The sentence don't change anything else should become a habit whenever you revise an Artifact that's almost done. This simple sentence keeps the parts that are already right safe.
Step 2: Managing versions
Versions are more than a label. There are three ways to use them. First, go back to an older version. For example: use version two, but keep the promo section. Second, compare two versions. Just ask: what changed from version three to version four? Claude will summarize the changes, a quick way to spot changes you didn't ask for. Third, version navigation in the panel. Some Claude layouts have buttons to switch between versions. Their position and look may differ, because Claude is updated often. Let's try the second way on the Sunset Coffee page. Laras asks: what changed from version two to version four? Claude makes a short list: version three added the promo and mistakenly changed the hamper price, then version four restored it. A list like this really helps once an Artifact has been revised many times. Laras saves this change list together with the final version of the page. If anyone ever asks why the price was different for a while, the record is there. The next question: keep revising in the same chat, or start a new one? Continue in the same chat as long as there have only been a few revisions. The advantage is that the version history stays complete. But after dozens of revisions and a very long conversation, Claude can lose focus. At that point, a new chat keeps the work tidier. It's easy: copy the latest version from the Code tab, open a new chat, paste it in, then explain the page's goal and the next change again. If you do this often, keep important Artifacts in a Project.
Step 3: Revising from other people's feedback
Revisions often come from other people too. Dewi sent a fourth-quarter sales summary to her manager, and got two pieces of feedback: add a column for the change from last quarter, and sort by largest sales. Dewi pastes the feedback as it is. Claude applies both and writes a summary of the changes below the table. Dewi can reply to her manager right away: the feedback has been applied, and here are the changes. Dewi still checks the third-quarter numbers against the old report. A new column means new numbers, and new numbers always need checking. From Dewi's example, there are four habits for taking feedback neatly. First, paste the feedback as it is, and number it if there's more than one point. Second, ask for it to be applied point by point, so each change is easy to check. Third, ask for a summary of the changes. This summary is useful for reporting back to the person who gave the feedback. Fourth, decide for yourself which feedback doesn't fit. Claude applies what's asked; judging the feedback is still your job.
Step 4: Options for sharing an Artifact
Now for sharing. The first way is a link from Claude, through the Artifact sharing or publishing feature, if it's available on your plan. Remember, anyone who has that link can open it. The second way: copy or download the content into Google Docs, Word, or a file. Recipients don't need a Claude account. The third way: a screenshot or print to PDF. Good for sending via WhatsApp, but calculators or checklists can no longer be clicked. Button names and the availability of sharing features can differ by plan and version. Check the official Claude documentation, including whether a shared link can be turned off later. Dewi chooses the method that fits her manager best: she downloads the summary as a PDF and sends it by email, replying to Mr. Surya's feedback message. Her email is short: both pieces of feedback have been applied, the PDF is attached, and the third-quarter numbers have been checked. The company's sales data isn't published through a public link, because it's internal. For the Sunset Coffee promo page, on the other hand, Laras uses a public link, because it's meant for everyone. So choose how to share based on the content, not on habit.
Step 5: Safety rules and session recap
Before sharing any Artifact, run through this checklist. First, all the content and numbers have been checked, not just the revised part. Remember the hamper price earlier. Second, the sharing method fits the nature of the content. A promo page can be public, a sales report stays internal, and student grades stay private. Third, a copy of the final version is saved on your computer or drive. And what must not be there: customers' personal data, students' data, or confidential business information in an Artifact you share. These four points take just a minute to run through, but they can prevent much bigger problems once an Artifact has spread. Let's look back at this session's journey. We started by getting to know Artifacts: the right panel, versions, Preview, and Code. Then we created an SOP document and a checklist you can tick. Next came tables and calculators for cost of goods, wholesale discounts, and student grades. After that, a one-page website for Sunset Coffee, without writing code. And today, revising with focus, managing versions, and sharing safely. Now you have your first Artifact ready to share.
Done!
The Artifacts session is complete. We've revised with the look, mark, ask, and check pattern, managed versions, taken feedback, and shared Artifacts safely. In the next episode we start the Daily Productivity session, beginning with building a weekly work plan with Claude, so your week runs more smoothly. See you there!
Practice exercises
Try these on your own after watching to lock in what you learned.
Revise one of your Artifacts three times, with one specific change per message
Go back to the previous version and compare it with the latest one
Run the safety checklist, then share the Artifact with one coworker and ask for feedback
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
52 video classes1,277 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.
