Chapter 09 · WEB
Artifacts: a deliverable beside the chat
An artifact is a separate deliverable beside the chat: a document, code, diagram or interactive experience. It supports iteration and export while keeping the conversation that led to it.
Video
Steps
- Request a defined output or start from a template in the Artifacts tab. Specify audience, format and what it should do.
- Open the result and inspect the display, not just Claude's description. For code, test behavior too. A correct-looking screen does not prove its controls work.
- Request a focused change and compare the new version with the previous one. If it breaks, ask for a fix and retest the same flow.
- Export an available format or share only after reviewing the audience. Publishing an artifact can disclose it to others. Check for secrets, private source files and personal details.
Common pitfall: Publishing or remixing a result is not permission to disclose the source material you supplied.
Hands-on exercise: Create a simple diagram, change one heading, inspect the new version and export it without publishing.
Filmed demo · Video is added in the media phase
Recap
Comprehension check
What should you check before sharing an artifact?
Recap
- An artifact is a separate deliverable
- Compare versions and test behavior
- Review the audience before publishing