Web Artifacts Builder

anthropics's avatarfrom anthropics
⭐52.5kstars🔀5.1kforks📁View on GitHub🕐Updated Jan 1, 1970
[Developer Tools]

When & Why to Use This Skill

The Web Artifacts Builder is a specialized suite of tools designed to create sophisticated, multi-component Claude.ai HTML artifacts. By leveraging a modern frontend stack—including React 18, TypeScript, Tailwind CSS, and shadcn/ui—it enables the development of complex web applications with advanced state management and routing. The tool streamlines the entire workflow from project initialization to bundling everything into a single, self-contained HTML file, ensuring high-fidelity UI/UX for AI-generated web content.

Use Cases

  • Case 1: Developing complex, interactive dashboards that require state management and professional-grade shadcn/ui components within a single Claude artifact.
  • Case 2: Creating multi-page web prototypes or internal tools that utilize React Router for navigation while maintaining a single-file delivery format.
  • Case 3: Building high-fidelity, responsive UI components using Tailwind CSS that need to be bundled with all dependencies for immediate preview in Claude.ai.
  • Case 4: Streamlining the frontend development lifecycle for AI agents by providing automated scripts for project setup, component integration, and asset inlining.
nameweb-artifacts-builder
descriptionSuite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
licenseComplete terms in LICENSE.txt

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 <project-name>
cd <project-name>

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