web-artifacts-builder

Automate creation and bundling of Claude-compatible HTML artifacts with React tooling.

1.9k|448|Updated Mar 14, 2025
One-click install
npx skills add https://github.com/BidingCC/BuildingAI --skill web-artifacts-builder-bidingcc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-artifacts-builder
Source: https://github.com/BidingCC/BuildingAI/tree/main/skills/web-artifacts-builder
Command: npx skills add https://github.com/BidingCC/BuildingAI --skill web-artifacts-builder-bidingcc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires vite, tailwindcss, postcss, autoprefixer, @types/node, tailwindcss-animate, class-variance-authority, clsx, tailwind-merge, lucide-react, next-themes, @radix-ui/react-accordion, @radix-ui/react-aspect-ratio, @radix-ui/react-avatar, @radix-ui/react-checkbox, @radix-ui/react-collapsible, @radix-ui/react-context-menu, @radix-ui/react-dialog, @radix-ui/react-dropdown-menu, @radix-ui/react-hover-card, @radix-ui/react-label, @radix-ui/react-menubar, @radix-ui/react-navigation-menu, @radix-ui/react-popover, @radix-ui/react-progress, @radix-ui/react-radio-group, @radix-ui/react-scroll-area, @radix-ui/react-select, @radix-ui/react-separator, @radix-ui/react-slider, @radix-ui/react-slot, @radix-ui/react-switch, @radix-ui/react-tabs, @radix-ui/react-toast, @radix-ui/react-toggle, @radix-ui/react-toggle-group, @radix-ui/react-tooltip, sonner, cmdk, vaul, embla-carousel-react, react-day-picker, react-resizable-panels, date-fns, react-hook-form, @hookform/resolvers, zod, and includes scripts (resource) components.

What problem does it solve?

Developed to streamline the creation of Claude.ai HTML artifacts by providing a ready-to-use frontend tooling stack (React, Tailwind, shadcn/ui) and a clear bundling workflow, eliminating manual setup overhead.

Core Features & Use Cases

  • Scaffolds multi-component artifacts using React, TypeScript, Tailwind CSS, and shadcn/ui for rich UI and routing.
  • Bundles artifacts into a single HTML file via Parcel and html-inline to simplify sharing in Claude conversations.
  • End-to-end workflow supported by scripts for initialization, development, bundling, and testing, enabling demos, knowledge bases, and interactive experiences.

Quick Start

Initialize a new project with scripts/init-artifact.sh <project-name>, then develop your artifact and finally run scripts/bundle-artifact.sh to generate bundle.html.

Frequently Asked Questions about web-artifacts-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bundle React components into a single HTML file for Claude artifacts?

Bundle React components for Claude artifacts into a single HTML file using the provided scripts/bundle-artifact.sh, which leverages Parcel and html-inline to inline all assets and generate a shareable bundle.html output.

Can I use shadcn/ui and Tailwind CSS when building Claude artifacts?

Yes, you can use shadcn/ui and Tailwind CSS when building Claude artifacts. The tooling scaffolds projects with these dependencies preconfigured, enabling rich UI components and styling for complex multi-component applications.

What is the best way to scaffold a multi-component React artifact with routing and state management?

The best way to scaffold a multi-component React artifact with routing and state management is running scripts/init-artifact.sh. It initializes a TypeScript, Vite, and React environment with the necessary UI dependencies out of the box.

Does this bundling workflow support Radix UI components for interactive experiences?

Yes, the bundling workflow supports Radix UI components. The initialization script includes extensive Radix UI dependencies, allowing you to build accessible interactive experiences and bundle them into a single HTML artifact.

Why do I need Vite and Parcel to generate a Claude-compatible HTML artifact?

You need Vite for local development and Parcel to bundle the React application. Parcel compiles the multi-component source code and html-inline inlines assets into a single Claude-compatible HTML artifact file.

Are there limitations when sharing bundled React artifacts in Claude conversations?

A limitation of sharing bundled React artifacts is that the final bundle.html inlines all JavaScript and CSS. Complex state management and routing must function entirely client-side within the single generated HTML file without external network requests.