web-artifacts-builder

Bundle React and Vite frontend projects into self-contained HTML artifacts.

18|6|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/alter123-zz/RaccoonClaw --skill web-artifacts-builder-alter123-zz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-artifacts-builder
Source: https://github.com/alter123-zz/RaccoonClaw/tree/main/skills/web-artifacts-builder
Command: npx skills add https://github.com/alter123-zz/RaccoonClaw --skill web-artifacts-builder-alter123-zz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires parcel, @parcel/config-default, parcel-resolver-tspaths, html-inline, vite, tailwindcss, postcss, autoprefixer, tailwindcss-animate, @types/node, 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?

Automates turning modern frontend projects into Claude-ready, self-contained HTML artifacts by automating initialization, bundling, and inlining of assets.

Core Features & Use Cases

  • Initialize a new React + Vite project with a single script, then bundle into a single HTML artifact for Claude conversations.
  • Bundle all JavaScript, CSS, and assets into bundle.html, enabling offline sharing and quick previews.
  • Supports Tailwind CSS and shadcn/ui components, path aliases, and a reproducible setup workflow for sharing.
  • Use cases include preparing portable UI prototypes for Claude chats, demos, and artifact-based explanations in conversations.

Quick Start

Initialize a new artifact project with the provided script, then bundle it into a single HTML artifact for Claude sharing.

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 a React and Vite project into a single HTML file?

Yes, you can bundle Tailwind CSS and shadcn/ui components into a single HTML artifact. The skill includes Tailwind CSS, Postcss, and Radix UI dependencies to ensure your styled components are packaged correctly into the final HTML file.

What are the environment requirements for bundling frontend projects into HTML artifacts?

Bundling frontend projects into HTML artifacts requires Node.js 18+ and PNPM as the package manager. These prerequisites ensure the bundling tools and scripts execute correctly to generate the self-contained HTML output.

Why package frontend UI prototypes into a single self-contained HTML file?

To bundle a React and Vite project into a single HTML file, this skill automates initialization and uses Parcel with html-inline to inline all JavaScript, CSS, and assets, producing a self-contained bundle.html for offline sharing.

Can I bundle Tailwind CSS and shadcn/ui components into a single HTML artifact?

Yes, you can bundle Tailwind CSS and shadcn/ui components into a single HTML artifact. The skill includes Tailwind CSS, Postcss, and Radix UI dependencies to ensure your styled components are packaged correctly into the final HTML file.

What are the environment requirements for bundling frontend projects into HTML artifacts?

Bundling frontend projects into HTML artifacts requires Node.js 18+ and PNPM as the package manager. These prerequisites ensure the bundling tools and scripts execute correctly to generate the self-contained HTML output.

Why package frontend UI prototypes into a single self-contained HTML file?

Packaging frontend UI prototypes into a single self-contained HTML file enables quick previews and offline sharing. This format creates Claude-ready artifacts, allowing you to easily share portable UI demos directly within Claude conversations.