Tonight’s wow-demo

The Stage

The impressive Claude demo you can run tonight is a one-prompt artifact prototype on Claude Opus 5. Paste the prompt below, ask Claude for a shareable interactive app, then check that the numbers actually change when you poke the inputs. Anthropic’s Help Center calls artifacts shareable apps, tools, or content, and published artifacts can be viewed by anyone with the link. This Stage is that reveal with the wires labeled: prerequisites, the copyable script, what should happen, and how to verify it. Claude will not give you an identical result twice; the proof is that you can inspect the artifact.

Cast: Opus 510-20 minutesBeginnerFounders, PMs, designers, educators

Why this demo, and not the whole cabinet

A gallery of ten scripts is useful after you already believe the trick is real. The Stage exists for the first night: one sourced wow-demo, one copyable prompt, one verification loop. The rest of the cabinet stays in the wings.

We picked the artifact prototype because it is the strongest existing MagicClaude demo for a live room. It is beginner-shaped, it does not need a repository or a PDF, and the reveal is something you can click. Anthropic’s artifact docs are the primary source, not a screenshot of someone else’s run.

This page is original MagicClaude editorial. Capability claims cite Anthropic. The prompt is ours. No transcript on this page is a Claude session; we describe what should happen and how you can falsify it.

"shareable apps, tools, or content"

Cue board

Walk the show, then steal the script

0 of 7 cues lit

Check a cue when it is true in your room. Copying the prompt lights the script lamp. None of this phones home; the lamps live in this browser.

House cues

Run this on Claude Opus 5. It is the default on Claude Max and the strongest model on Pro, so most audiences can reproduce the reveal on their own seat without API access. Rehearse on Sonnet 5 if you want faster iteration while you tune the idea.

Proof cues

A demo is not a screenshot. Mark a cue only after you have done the check, not because the output looked polished.

The script

Copy this into Claude

Run it on Claude.ai or the desktop app with code execution and file creation enabled. The idea inside the prompt is synthetic on purpose: a meeting-cost theater, not your payroll.

Plain-text promptOpus 5 · artifacts
<role>You are a product designer and front-end prototyper.</role>
<goal>Create a shareable Claude artifact for a tiny interactive product demo.</goal>
<idea>
I need a "meeting-cost theater" that lets a team enter meeting length, attendees,
average hourly rate, and recurring cadence. It should reveal the monthly cost,
show a dramatic stage-style breakdown, and suggest one meeting redesign.
</idea>
<requirements>
- Before coding, list the core screens, states, and edge cases.
- Build a polished single-page interactive artifact.
- Include empty, normal, and extreme-value states.
- Add a short "what to verify before sharing" checklist below the UI.
- Keep all sample data synthetic.
</requirements>

After it builds, you can ask for a tone change, a unit change, or a second empty state without starting over. If you need a themed variant, use the prompt remixer rather than inventing a new shape.

The reveal, without a fake transcript

A vague idea becomes something you can click. The important move is asking Claude to expose states and tradeoffs before it writes the artifact, so the result feels designed rather than merely generated.

What should happen, in a room you can inspect:

  • Claude should first describe a compact interaction plan rather than rushing into code.
  • The artifact should include form inputs, a calculated reveal, and a visible checklist.
  • Follow-up prompts can change tone, labels, units, or layout without starting over.

This is not production software. It proves that Claude can draft a standalone interactive artifact quickly, not that the output has passed security, accessibility, or product-market validation. If you need a scored comparison of Opus 5 against Fable 5.1, that work belongs toClaude Reports, not this stage.

Guardrails for a live room

  • Replace sensitive company rates with ranges or synthetic values.
  • Treat generated calculations as draft logic; verify formulas manually.
  • If publishing, verify that every embedded domain and attachment is intentional.
  • Say the model name out loud before you paste. A prompt without a cast becomes unreproducible the next time Anthropic ships.

If the trick goes sideways

Funny, weird, or slapstick outputs belong at Claude Gone Wild. Do not paste private data into an outtake, and do not file a funny fail as a MagicClaude transcript. This site does not publish session logs.

If what you actually want is an experiment—change one variable, write a method, chase an edge case—take it toCurious Claude. The Stage is a wow-demo with receipts, not a lab bench.

The understudy, not a second spotlight

When the room is already convinced and you want a longer night, the next sourced demo is thelong-horizon agent run on Claude Fable 5.1. Anthropic positions Fable 5.1 for demanding reasoning and long-horizon agentic work. It is the wrong opening number: slower, more supervised, and easy to confuse with a benchmark if you narrate it badly.

The current lineup, API IDs, and wrong-cast notes live on the casting page.

Primary Sources

These demos cite official Anthropic docs or help-center pages for capability claims. They do not claim identical output across accounts, plans, models, or dates.

Claude Help Center

Publish and share artifacts

Free, Pro, and Max users can publish artifacts publicly; Team and Enterprise sharing is organization-scoped.

Claude Platform Docs

Prompting best practices

Anthropic guidance emphasizes explicit instructions, output formats, tool-use direction, and model-specific prompt updates.

Claude Platform Docs

Claude Opus 5 overview

Claude Opus 5 (`claude-opus-5`) launched July 24, 2026 with a 1M-token context window, 128K max output, adaptive thinking, and an optional fast mode.