SYSTEM DOCUMENTATION & REQUIREMENTS
💡 This Skill requires parcel, @parcel/config-default, parcel-resolver-tspaths, html-inline, 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?
Creating Claude-ready artifacts from multi-file frontend projects is tedious and error-prone without an automated bundling workflow that produces a single portable artifact.
Core Features & Use Cases
- Single-file artifact generation: bundle React apps into a self-contained HTML artifact suitable for Claude conversations.
- Frontend tooling support: integrates Tailwind CSS, shadcn/ui components, and Vite-based workflows for rapid prototyping.
- Reusable automation: includes scripts to initialize, bundle, and verify artifacts, enabling repeatable Claude-ready outputs across projects.
Quick Start
Run the initialization script to create a new React artifact project and then bundle it into a single HTML file.