Pick the prompt by proof shape
A Claude prompt example should answer one question before it tries to impress anyone: how will the viewer know it worked? For an artifact, the proof is clickable behavior. For a PDF, the proof is a page-anchored evidence table. For a screenshot, the proof is visible evidence and confidence labels. For research, the proof is source quality and unknowns.
Use a three-part setup
- Scene: tell Claude the role, audience, and input boundary.
- Reveal: state the artifact, table, chart, memo, or critique the audience should see.
- Inspection: require assumptions, guardrails, and verification steps in the output.
Fast prompt choices by room
- Executive meeting: use a long-context synthesis or web research brief with unknowns and source links.
- Product team: use a screenshot UX audit or artifact prototype with visible states.
- Analyst room: use a PDF evidence table or CSV-to-visual prompt with formulas exposed.
- Creative workshop: use an SVG poster or one-prompt artifact, then inspect accessibility and editability.
What to avoid
Avoid prompts that depend on private data, hide model uncertainty, or claim product behavior that the viewer cannot inspect. The point is not to remove the theatrical reveal; it is to keep the wires labeled so the reveal survives scrutiny.