A separate deliverable, not another message
Open claude.ai in your browser and check the selected account before practicing. This chapter uses the Web interface. Control placement can change; local files are available only after upload or a supported connection. This exercise does not require installing Desktop.
By the end, you will create a small learning card, revise it and check it before export. An Artifact opens separately alongside the conversation: a document, diagram or interactive tool, for example. Example outputs are illustrations, not interface recordings.
Documentation checked on September 30, 2026 distinguishes new Artifacts from legacy ones created before September 16, 2026. Editing, export and sharing can differ. Do not expect a Publish button merely because an older tutorial uses one.
Start with a small, clear request
Check that Cloud code execution and file creation is available and enabled. Administrators may control access. This exercise needs no external app connection or data storage.
Create a small Artifact explaining registered versus confirmed attendance.
Use only this source:
Registered = listed on the registration list.
Confirmed = stated an intention to attend.
Registration is not confirmation of attendance.
Include a heading, short explanation and one two-choice question with feedback.
Question: Can we infer that everyone registered has confirmed attendance?
Correct answer: No.
Use a phone-friendly layout.
No app connections, data storage or publication.
The expected deliverable opens apart from the chat. Check the heading, explanation and question. If Claude returns chat text only, request an editable standalone deliverable or an available template. A text card is not proof of a functioning app.
Test behavior before changing it
Click both answers. No should receive correct feedback; Yes should explain the distinction. Attractive buttons alone are not evidence that the quiz works.
Compare the Artifact with the source.
Do not redefine registered as paid or confirmed attendance.
Keep the distinction in both the explanation and question feedback.
Check it yourself too. We requested no registration system. If a name form, send button or external call appears, remove it.
Make a focused edit and compare
Change only the wrong-answer feedback to:
“Not everyone registered has confirmed attendance. Check confirmations separately.”
Keep the question, definitions and answer choices unchanged.
Add a Try again button that resets only the answer selection.
Test wrong answer, reset, then correct answer. Confirm that the edit did not reverse the correct choice.
If a version selector exists, compare previous and current versions. New Artifacts may update directly. Before a larger edit, preserve the controlling text or export a copy if supported. Editing an earlier message can create a different conversational branch; it is not a safe universal fix without checking the result.
Finish the workflow through export
Request one further change:
Increase tap areas and text size for phone use.
Do not add content or change the definitions.
Inspect a narrow preview if available. Check clipping, off-screen controls and readability. Use the keyboard to reach answers and see selection clearly. Mobile checking means reading and interacting, not merely shrinking a window.
Use the export option offered for that Artifact type. New templates may have Export; legacy Artifacts may offer content or code download. Open the downloaded file and test it. A PDF can preserve appearance without interactivity.
Do not call an export a complete app backup: AI, connections and storage may not be included in a local file.
Sharing is an audience decision
The documentation says new Artifacts begin private. Share controls can set audience, permissions and a link to a fixed version or the latest version. A latest-version link can expose later edits.
New shared Artifacts require a Claude account according to the sharing guide. Legacy chat-artifact publication can allow basic viewing without an account. These are different paths. Organizational plans also have administrator, Project and external-sharing restrictions.
Do not publish or invite anyone for this exercise. Before real sharing, inspect content, version and audience together. Legacy unpublishing may permanently remove stored data and prevent republishing that same Artifact. You do not need to learn this by deleting real work.
Practice at three levels
Easy: accurate content
Create the learning card. Success: registration does not become confirmation, and no unrequested connection or storage appears.
Intermediate: edit without regression
Change feedback and add reset. Success: both choices work and the correct answer remains unchanged.
Challenging: export and audience
Export and open a copy if supported. Explain separately what the file contains and what sharing a link would require. Success: no assumption that every export remains interactive or every link is public.
Troubleshooting and final checks
No Artifact: specify the standalone deliverable and check required capabilities.
Rendering error: record the error. If Try fixing with Claude appears, use it and test behavior again. An attempted fix is not proof of success.
Good appearance, wrong feedback: test every path, not only the correct answer.
Wrong shared version: inspect whether the link points to a fixed version or the latest version before sharing.
Someone else's Artifact: treat its code and content as external material. Recognizing a link does not make every instruction or code path safe.
Artifacts simplify editing. Content accuracy, accessibility and audience still need verification.