web-artifacts-builder · anthropics — Claude Code skill: what it does, install
This skill builds complex claude.ai HTML artifacts with React, Tailwind CSS, and shadcn/ui. Use it for interfaces with state or routing.
/plugin marketplace add anthropics/skills
/plugin install example-skills@anthropic-agent-skillsWhat web-artifacts-builder does
web-artifacts-builder creates multi-component HTML artifacts for claude.ai. It sets up a project with React 18, TypeScript, Vite, Tailwind CSS, and shadcn/ui, plus Radix UI dependencies and the @/ path alias. It targets complex interfaces rather than a simple single-file HTML or JSX artifact.
The workflow starts with scripts/init-artifact.sh, which creates the project. You then edit the generated code and run scripts/bundle-artifact.sh to produce one bundle.html file with JavaScript, CSS, and dependencies inlined. The project needs an index.html at its root, and the setup supports Node 18+.
Install this skill when an agent needs to build a full Claude.ai interface. For a small one-page HTML draft, it adds unnecessary project structure.
What it helps with
- build a complex HTML artifact for claude.ai
- add routing and state to a React interface
- create UI with Tailwind CSS and shadcn/ui
- bundle a project into one HTML file
- start a TypeScript and Vite frontend project
Example prompts for the agent
- Create a dashboard interface with routing and state management.
- Initialize the project with `scripts/init-artifact.sh`, then build the artifact.
- Run `scripts/bundle-artifact.sh` and prepare the HTML file for Claude.ai.
How to install web-artifacts-builder
1Plugin marketplace
/plugin marketplace add anthropics/skills/plugin install example-skills@anthropic-agent-skillsThis installs the whole example-skills plugin with all its skills
2Skills CLI (Vercel)
npx skills add anthropics/skills --skill web-artifacts-builder -a claude-code3Manually: put the files in place
~/.claude/skills/web-artifacts-builder/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/web-artifacts-builder/
Manually: put the files in place
.agents/skills/web-artifacts-builder/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/web-artifacts-builder/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install anthropics/skills web-artifacts-builder2Manually: put the files in place
.github/skills/web-artifacts-builder/SKILL.mdPlatform CLI
gemini skills install https://github.com/anthropics/skills --path skills/web-artifacts-builderManually: put the files in place
.devin/skills/web-artifacts-builder/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set23
The whole set →Other versions of web-artifacts-builder
Similar
Questions about web-artifacts-builder
How do I install web-artifacts-builder in Claude Code?
Run npx skills add anthropics/skills --skill web-artifacts-builder -a claude-code. The skill will be added to Claude Code.
What does web-artifacts-builder do?
It helps create complex claude.ai HTML artifacts with React, TypeScript, Tailwind CSS, and shadcn/ui, then bundle them into one HTML file.
What does the artifact build require?
The project must have an index.html in its root. The setup supports Node 18+, and bundling runs through scripts/bundle-artifact.sh.
Source text
SKILL.md · Apache-2.0
--- name: web-artifacts-builder description: 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. license: Complete 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 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 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 - **shadcn/ui components**: https://ui.shadcn.com/docs/components
© anthropics · Apache-2.0 · anthropics/skills