Percerno Skillsbeta
← everything it can do · engineering

Web Artifacts Builder TEXT

Builds complex, interactive frontend applications using React, TypeScript, Tailwind CSS, and shadcn/ui, then bundles them into a single self-contained HTML file for display as a claude.ai artifact.

2 uses this weeksource anthropicslicence Apache-2.0needs internet for packages
Quality gate: FAIL · better answers · measured 2026-10-24
Blind-judged against the bare model on 2 requests: average lift -30.5 points (specificity, structure, method, fit).
won 0/2, lift -30.5, tokens ×45.37
Security scan: review · 2026-10-24 · 4 files · ran in sandbox
something a person should read before trusting it: destructive ×1, external-hosts ×1 · hosts: www.apache.org, ui.shadcn.com.

Try asking

Say it in your own words; the assistant finds this recipe by itself. Examples:

“Lav en interaktiv kalender med muligheden for at tilføje og slette begivenheder.”
“Byg et dashboard til at overvåge serverstatus med live opdateringer.”
“Jeg har brug for en formular til at indsamle feedback med flere trin.”
“Create a Kanban board with drag-and-drop functionality using shadcn/ui components.”
“Build a multi-step checkout form with validation and state management.”
“I need a dashboard for tracking crypto prices with real-time updates and charts.”
Try this skill from Claude, ChatGPT or a chat on your own page. Free plan, no credit card.Get started free

Good for

reacttypescripttailwind-cssshadcn-uihtml-artifactfrontendbundlinginteractive-uiweb-app

Not for

Do not use this skill for simple, static single-file HTML or JSX snippets that do not require a build process or component libraries. For basic data visualization or simple scripts, a standard code execution or simple HTML generation skill is more appropriate.

Details

When it is the right choice

Use this skill when the user requests a complex, multi-component web interface or application that requires state management, client-side routing, or specific UI component libraries like shadcn/ui. It is ideal for creating rich, interactive dashboards, forms, or mini-apps that need to be delivered as a single, shareable HTML artifact.

The full recipe the assistant reads

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

  • shadcn/ui components: https://ui.shadcn.com/docs/components
Files in this skill (5)
  • LICENSE.txt
  • SKILL.md
  • scripts/bundle-artifact.sh
  • scripts/init-artifact.sh
  • scripts/shadcn-components.tar.gz
Where it comes from

Vendored from anthropics/skills, commit dbd4588f9e10, path skills/web-artifacts-builder, licence Apache-2.0. The upstream licence file ships inside the skill.