web-artifacts-builder is one of the example skills in Anthropic’s public skills repository. It is meant for elaborate, multi-component claude.ai HTML artifacts that need state management, routing or shadcn/ui components, and its own description says it is not for simple single-file HTML or JSX artifacts. Instead of writing one file by hand, Claude sets up a real frontend project, develops in it, and bundles the result.
The workflow is five steps: run scripts/init-artifact.sh to create a React 18 and TypeScript project with Vite, Tailwind CSS 3.4.1, the shadcn/ui theme, an @/ path alias and over 40 shadcn/ui components; edit the generated code; run scripts/bundle-artifact.sh to build it with Parcel and inline every script, style and dependency into one bundle.html; share that file as the artifact; and, only if needed or asked, test it afterwards. The skill also tells Claude to avoid the look often called “AI slop”: excessive centered layouts, purple gradients, uniform rounded corners and the Inter font.
What You Get
- scripts/init-artifact.sh, which creates a React 18 + TypeScript + Vite project configured for Tailwind CSS 3.4.1, the shadcn/ui theming system and the @/ import alias
- Over 40 shadcn/ui components, from accordion and dialog to table, tabs and tooltip, extracted from a bundled archive into the project’s src folder, with their Radix UI and supporting dependencies installed
- A light and dark shadcn theme written as CSS variables, plus a components.json for reference
- scripts/bundle-artifact.sh, which builds the app with Parcel without source maps and inlines every asset into one bundle.html
- Node version handling: Node 18 or newer is required, and Vite is pinned to 5.4.11 on Node 18
- A short style rule to avoid excessive centered layouts, purple gradients, uniform rounded corners and the Inter font
Common Use Cases
- Building a multi-screen claude.ai artifact with routing or shared state that would be awkward as one hand-written file
- Making an interactive dashboard or tool from shadcn/ui components such as tables, tabs, dialogs and forms
- Prototyping a React UI with TypeScript and Tailwind, then delivering it as a single HTML file anyone can open
- Packaging an existing small React app with an index.html at its root into one self-contained artifact
What Makes It Unique
Most of Anthropic’s design skills in this directory are guidance: frontend-design shapes how Claude thinks about palette, type and layout, and algorithmic-art writes one HTML page that loads p5.js from a CDN. web-artifacts-builder is tooling instead. Its two shell scripts do most of the work, standing up a full Vite, Tailwind and shadcn/ui project with dependencies installed locally, then compiling and inlining it so the finished artifact carries all of its code inside one file. It is aimed at the complex end of artifacts and says outright that simple single-file ones do not need it.
Under The Hood
The skill is a SKILL.md, two shell scripts, a gzipped archive and the license text. Claude runs the scripts in a shell, and their frontmatter does not mention this. init-artifact.sh checks the Node version, installs pnpm globally with npm if it is missing, and runs pnpm create vite with the react-ts template, so it downloads packages from the npm registry: Tailwind, PostCSS, Autoprefixer, about two dozen Radix UI packages, and libraries such as lucide-react, sonner, cmdk, react-hook-form and zod. It writes config files into the new project folder (postcss.config.js, tailwind.config.js, vite.config.ts, src/index.css, components.json), edits index.html and both tsconfig files with sed and short node scripts, and unpacks the archive into src. The skill says that archive holds the shadcn/ui component files, but it is a binary file that cannot be read as text, so what it contains has not been checked here. bundle-artifact.sh, run from the project root, adds Parcel, a path-alias resolver and html-inline as dev dependencies, writes a .parcelrc if there is none, deletes any previous dist folder and bundle.html, builds, and writes the inlined bundle.html. Nothing is deployed or sent anywhere; the file is shared in the conversation. Testing, if it happens, uses whatever tools are available, such as Playwright or Puppeteer.