SkillsAdd

anthropics/skills · Official

web-artifacts-builder

Suite 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.

All-time #321 Trending #682 Hot #6299 First seen Jan 19, 2026
8-week activity · all time api

Installation

$ npx skills add anthropics/skills --skill web-artifacts-builder
View on skills.sh ↗ GitHub repository ↗

Summary

  • Multi-component React artifacts for Claude with bundling, state management, and shadcn/ui component library.
  • Scaffolds React 18 + TypeScript projects with Vite, Tailwind CSS, and 40+ pre-installed shadcn/ui components via automated initialization script Bundles complete artifacts into single self-contained HTML files with inlined assets, ready for Claude artifact display Includes design guidance to avoid common "AI slop" patterns like excessive centering, purple gradients, and uniform rounded corners Supports complex workflows requiring routing, state management, and Radix UI dependencies out of the box

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

vercel-react-best-practices Shared topics
vercel-labs/agent-skills 697.8K installs
azure-hosted-copilot-sdk Shared topics
microsoft/azure-skills 440.4K installs
vercel-composition-patterns Shared topics
vercel-labs/agent-skills 326.5K installs
vercel-react-native-skills Shared topics
vercel-labs/agent-skills 205.5K installs
artifacts-builder Similar name
composiohq/awesome-claude-skills

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern fr…

3.9K installs
web-artifacts-builder Similar name
nexu-io/open-design

Build complex claude.ai HTML artifacts with React and Tailwind. Anthropic's reference workflow …

2.5K installs

Security audits

Partner security reviews for this skill.

agent-trust-hub SAFE

Analyzed Apr 21, 2026

This skill provides a suite of tools for building complex React-based artifacts for Claude. It automates the setup, development, and bundling process using standard web development tools like Vite, Parcel, and Tailwind CSS. The security analysis found the skill to be safe, with all external dependencies being well-known and used within their intended scope.

snyk LOW

Analyzed Apr 21, 2026

No issues detected.

socket Score 0.9000 · 0 alerts

Analyzed Apr 21, 2026

  • license 1
  • maintenance 1
  • quality 0.9
  • supply chain 1
  • vulnerability 1

0 alerts

Also in this package

Other skills from anthropics/skills · top by installs.

npx skills add anthropics/skills
frontend-design 866.4K skill-creator 375.6K pptx 216.8K pdf 192.4K docx 184.5K xlsx 165K webapp-testing 152.3K mcp-builder 112.3K canvas-design 105.8K brand-guidelines 88.5K

Browse all from anthropics/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 175.2K
License Complete terms in LICENSE.txt
Default branch main
Open issues 1,222
Last push Sep 3, 2026
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseComplete terms in LICENSE.txt

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,087 B
  • docs SUMMARY.md 314 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 99,122 installs

SKILL.md

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