How to Create and Improve Artifacts with Claude

Artifacts are standalone pieces of content that Claude creates in a dedicated panel alongside the conversation. Instead of getting a code snippet or document buried in a chat reply, you get a separate, editable output you can iterate on. Artifacts are available when code execution and file creation are enabled in Settings > Capabilities — check your plan and settings for availability.

What you can create as Artifacts

• Documents — reports, briefs, proposals, guides
• Code — scripts, components, configuration files
• HTML/CSS — interactive previews, landing page mockups
• SVG and visual content — diagrams, charts, simple graphics
• Markdown — structured content you can export

Creating your first Artifact

Ask Claude to create something that is clearly a standalone output. Claude decides whether to use an Artifact or inline text based on the content. For reliable Artifact creation, ask for something self-contained.

Bad

Write some code.

Better

Create a Python script that converts CSV files to JSON. Include error handling for missing files and malformed rows.

Best

Create a Python script: csv_to_json.py

Requirements:
- Takes an input CSV file path and output JSON file path as command-line arguments
- Handles: missing file, empty file, malformed rows (skip and log)
- Output: array of objects where keys are column headers
- Include a usage comment at the top
- Use only standard library (no pandas)

After creating the script, explain how to run it with an example command.

Iterating on Artifacts

The real value of Artifacts is iteration. Instead of starting over, tell Claude what to change about the existing Artifact.

Update the script:
1. Add a --delimiter flag that defaults to comma but accepts tab or pipe
2. Add a --pretty flag for indented JSON output
3. Keep the existing error handling unchanged

Each update modifies the Artifact in place. You can see the version history and go back to earlier versions if a change went wrong.

Editing Artifacts directly

For Markdown Artifacts, you can edit the content directly in the Artifact panel using the Edit with Claude feature. This is faster than describing every small change in the chat. Make your edits, then ask Claude to review or continue from the edited version.

Practical Artifact workflows

• Draft a project proposal as a document Artifact, iterate through review rounds, then export
• Build an HTML prototype of a landing page, refine the layout and copy in stages
• Create a data processing script, test with sample data, add features incrementally
• Design an SVG diagram of your system architecture, then update it as the design evolves

Common Artifact mistakes

• Asking for changes without specifying what to keep — Claude may rewrite sections you liked
• Not using the version history when an iteration goes wrong
• Creating multiple separate Artifacts when you should iterate on one
• Forgetting that Artifacts need the right settings enabled — check Settings > Capabilities if Artifacts are not appearing

Related reading: /blog/how-to-use-claude-projects for project-level context and /blog/how-to-build-a-reusable-claude-workflow for saving workflows you repeat.