Start with the decision, not the whole session
Take this fictional change: shipping should become free at $50, but the old condition charged shipping on an order of exactly $50. The useful review is small. Show the old condition, the replacement, and three amounts on either side of the boundary.
The accompanying original HTML example does exactly that. Choose $49.99, $50, or $75. It calculates both outcomes from integer cents and marks the one case where the result changes. It is an authored practice page, not a screenshot of Claude or a published Claude artifact.
That gives the reviewer something specific to approve: whether $50 itself belongs on the free-shipping side. The example does not pretend to establish the store's real policy. Replace the fictional rule with the requirement your team has actually agreed to.
Open the interactive example · Open the standalone HTML
Ask for a native artifact explicitly
Ask for an artifact and describe the review you need. Claude Code's documented output includes a claude.ai URL. Availability requires an eligible plan and a claude.ai login. Native artifact creation and availability
Use a request with a clear boundary:
Create a Claude Code artifact for reviewing [CHANGE OR PR].
Reviewer: [ROLE]. Decision needed: [EXACT QUESTION].
Use only these approved files or excerpts: [LIST].
Show the requirement, the relevant before/after code, and the cases that
distinguish the two versions. Preserve the units and boundary conditions.
Keep observed test results separate from expected results. Do not invent
passing tests, production data, an approval, or a deployment.
Keep the artifact private. Show me the page and its URL before changing
sharing settings. Do not include credentials, unrelated session content,
customer records, or connected live data.
If you want the independent version instead, ask for one complete HTML file with its styles and JavaScript inside it. Request sample data or approved excerpts rather than links to private source systems. Our Claude Code HTML files guide covers that file-based route.
Choose the version and audience before sending
Native artifacts start private. Claude Code's documentation describes sharing from the page header and selecting the version viewers receive. It also describes updating an existing artifact by supplying its URL or attaching it with /artifacts; a new session without that reference can create a separate artifact. Sharing and updates
For a change review, write the reviewed revision into the page itself. “Shipping threshold — revision B” is more useful than “Latest results” when someone is comparing an earlier decision with a later change.
Then inspect the actual Share control for your account. Choose the intended audience and test the resulting link as the intended recipient before relying on it. A URL copied from your own signed-in tab does not prove what someone else will see.
A connected dashboard needs another check
The Claude Code documentation says connector calls use the viewer's own connections. A reviewer can therefore see a page without the live section you see. Mark a section as live only if it really makes a supported connection, and label a captured value with the time and source it represents. Connector-backed artifacts
The shipping example avoids that dependency. Its three fictional cases and calculations are in the file. The reviewer can inspect the boundary without access to a repository, order system, or live connector.
Send the deliverable that fits the review
Keep the native artifact when your review depends on its sharing controls, versions, or connected features. For an approved, self-contained HTML review copy, the next step can be turning that HTML into a NOS link. Keep the source change and authoritative test results in the repository; the review page explains them.
Before you send either version, finish this sentence: “Please check [case] against [requirement] and tell me whether [decision].” If the page cannot answer that request, adding more session output will not fix it.
For work moving from the standalone design site, prepare the project archive and an independent reading copy before confirming the transition.
If a downloaded copy loses a feature, inspect its HTML export dependencies before choosing another host.