Coding

web-artifacts-builder

Try it

Build React artifacts with a configured UI stack and bundle them into one self-contained HTML file.

What it does

Scaffolds a React 18 and TypeScript artifact project with Vite, Tailwind CSS, shadcn/ui, Radix UI dependencies, and path aliases. After development, its bundling script uses Parcel and html-inline to produce a self-contained `bundle.html` with JavaScript, CSS, dependencies, and assets inlined for sharing in Claude conversations.

When to use it

  • Starting a React artifact project
  • Building interfaces with shadcn/ui components
  • Bundling an artifact for a Claude conversation
  • Preparing a self-contained HTML deliverable

The skill document

Web Artifacts Builder

To build powerful frontend claude.ai artifacts, follow these steps:

  1. Initialize the frontend repo using scripts/init-artifact.sh
  2. Develop your artifact by editing the generated code
  3. Bundle all code into a single HTML file using scripts/bundle-artifact.sh
  4. Display artifact to user
  5. (Optional) Test the artifact

Stack: React 18 + TypeScript + Vite + Parcel (bundling) + Tailwind CSS + shadcn/ui

Design & Style Guidelines

VERY IMPORTANT: To avoid what is often referred to as "AI slop", avoid using excessive centered layouts, purple gradients, uniform rounded corners, and Inter font.

Quick Start

Step 1: Initialize Project

Run the initialization script to create a new React project:

bash scripts/init-artifact.sh 
cd

This creates a fully configured project with:

  • ✅ React + TypeScript (via Vite)
  • ✅ Tailwind CSS 3.4.1 with shadcn/ui theming system
  • ✅ Path aliases (@/) configured
  • ✅ 40+ shadcn/ui components pre-installed
  • ✅ All Radix UI dependencies included
  • ✅ Parcel configured for bundling (via .parcelrc)
  • ✅ Node 18+ compatibility (auto-detects and pins Vite version)

Step 2: Develop Your Artifact

To build the artifact, edit the generated files. See Common Development Tasks below for guidance.

Step 3: Bundle to Single HTML File

To bundle the React app into a single HTML artifact:

bash scripts/bundle-artifact.sh

This creates bundle.html - a self-contained artifact with all JavaScript, CSS, and dependencies inlined. This file can be directly shared in Claude conversations as an artifact.

Requirements: Your project must have an index.html in the root directory.

What the script does:

  • Installs bundling dependencies (parcel, @parcel/config-default, parcel-resolver-tspaths, html-inline)
  • Creates .parcelrc config with path alias support
  • Builds with Parcel (no source maps)
  • Inlines all assets into single HTML using html-inline

Step 4: Share Artifact with User

Finally, share the bundled HTML file in conversation with the user so they can view it as an artifact.

Step 5: Testing/Visualizing the Artifact (Optional)

Note: This is a completely optional step. Only perform if necessary or requested.

To test/visualize the artifact, use available tools (including other Skills or built-in tools like Playwright or Puppeteer). In general, avoid testing the artifact upfront as it adds latency between the request and when the finished artifact can be seen. Test later, after presenting the artifact, if requested or if issues arise.

Reference

Questions people ask

What does the initialization script configure?
It creates a React and TypeScript project via Vite, with Tailwind CSS 3.4.1, shadcn/ui theming, 40+ pre-installed shadcn/ui components, Radix UI dependencies, `@/` path aliases, and Parcel configuration.
What does the bundling step produce?
Running `scripts/bundle-artifact.sh` creates `bundle.html`. It builds without source maps and inlines the app’s JavaScript, CSS, dependencies, and assets into one self-contained HTML file.
Does the artifact need to be tested before sharing?
No. Testing is optional and should generally happen after presenting the artifact, when requested or when issues arise; Playwright, Puppeteer, or other available tools may be used.

Related skills

中国3C营销助手

Turn China 3C launch inputs into executable routes, messaging, channel actions, risk checks, and review decisions.

by killsnake0126 installs112 stars

figma-use

Official

Runs Figma Plugin API scripts with the required call parameters, API rules, IDs, and validation workflow.

by OpenAI28.0k stars

cli-creator

Official

Build and install a composable CLI with stable JSON, explicit auth, safe commands, tests, and companion guidance.

by OpenAI28.0k stars

aspnet-core

Official

Build and improve ASP.NET Core apps using focused, current framework guidance.

by OpenAI28.0k stars

algorithmic-art

Official

Create a seeded p5.js artwork, its algorithmic manifesto, and an interactive parameter viewer.

by Anthropic180.3k stars

skill-creator

Official

Create and refine agent skills through structured drafting, testing, comparison, and user review.

by Anthropic180.3k stars

More from Anthropic

Browse all skills

doc-coauthoring

Official

Guides documentation from context gathering through section-by-section drafting and reader testing.

by Anthropic180.3k stars

docx

Official

Create, read, edit, validate, and visually inspect .docx documents.

by Anthropic180.3k stars

pdf

Official

Read, create, extract, merge, split, rotate, watermark, OCR, and protect PDF files.

by Anthropic180.3k stars

pptx

Official

Create, inspect, edit, and validate PPTX decks and POTX templates.

by Anthropic180.3k stars

xlsx

Official

Create, edit, inspect, and validate spreadsheet files while preserving formulas, formatting, and workbook conventions.

by Anthropic180.3k stars

algorithmic-art

Official

Create a seeded p5.js artwork, its algorithmic manifesto, and an interactive parameter viewer.

by Anthropic180.3k stars