artifacts-builder
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/artifacts-builder --openclawArtifacts Builder
To build powerful frontend claude.ai artifacts, follow these steps:
- Initialize the frontend repo using
scripts/init-artifact.sh - Develop your artifact by editing the generated code
- Bundle all code into a single HTML file using
scripts/bundle-artifact.sh - Display artifact to user
- (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
.parcelrcconfig 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
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/artifacts-builder/SKILL.mdView on GitHub Overview
Artifacts-builder is a suite for creating elaborate, multi-component claude.ai HTML artifacts using React, TypeScript, Vite, Parcel bundling, Tailwind CSS, and shadcn/ui. It targets complex artifacts that need state management, routing, or shadcn/ui components, not simple single-file HTML artifacts.
How This Skill Works
Start by initializing a new React project with scripts/init-artifact.sh, then develop your artifact by editing the generated code. When ready, bundle everything into a single HTML file with scripts/bundle-artifact.sh, which produces bundle.html with all assets inlined for easy sharing in Claude conversations.
When to Use It
- You need a Claude.ai artifact with multiple components and routing.
- Your artifact requires client-side state management across views.
- You want to leverage shadcn/ui components within the artifact.
- You need a self-contained, inlined HTML artifact suitable for Claude sharing.
- You want a repeatable workflow using init-artifact.sh and bundle-artifact.sh.
Quick Start
- Step 1: bash scripts/init-artifact.sh <project-name> and cd <project-name>
- Step 2: Edit the generated code to build your artifact with React + TS and Tailwind + shadcn/ui
- Step 3: bash scripts/bundle-artifact.sh to create bundle.html (inlines JS/CSS); ensure index.html exists
Best Practices
- Plan the artifact architecture to maximize clear state flow and navigation.
- Follow the design guidelines to avoid AI slop (avoid excessive centering, purple gradients, uniform rounded corners, and the Inter font).
- Keep an index.html at the project root to satisfy bundling requirements.
- Regularly bundle with bundle-artifact.sh to validate inlining of assets.
- Document artifact metadata and component usage for maintainability and reuse.
Example Use Cases
- A multi-step onboarding flow with routing and stateful form inputs.
- A dashboard with draggable panels and real-time data (mocked) using React state.
- A settings panel with nested, shadcn/ui-based components.
- An interactive tutorial artifact guiding users through features step-by-step.
- A design-system showcase demonstrating Tailwind + shadcn/ui components in one artifact.
