artifacts-builder
npx machina-cli add skill mattmre/EVOKORE-MCP/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/mattmre/EVOKORE-MCP/blob/main/SKILLS/DEVELOPER TOOLS/artifacts-builder/SKILL.mdView on GitHub Overview
Artifacts Builder is a suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend technologies (React, Tailwind CSS, shadcn/ui). It’s intended for complex artifacts requiring state management, routing, or shadcn/ui components, and not for simple single-file HTML/JSX artifacts.
How This Skill Works
It scaffolds a React + TypeScript project (via Vite) with Tailwind CSS and shadcn/ui, then bundles everything into a single HTML file using scripts/bundle-artifact.sh. The result is bundle.html with all JavaScript, CSS, and dependencies inlined, ready to share in Claude conversations.
When to Use It
- When you need a multi-component Claude artifact with routing and state management.
- When you want a self-contained artifact that can be shared as one bundle.html file.
- When your UI uses Tailwind + shadcn/ui components and Radix UI dependencies.
- When you’re starting a new artifact project and want a standardized setup.
- When you need to test or preview the artifact locally before sharing.
Quick Start
- Step 1: Initialize Project - Run bash scripts/init-artifact.sh <project-name> and then cd <project-name>
- Step 2: Develop Your Artifact - Edit the generated files to implement the UI and logic
- Step 3: Bundle to Single HTML File - Run bash scripts/bundle-artifact.sh to produce bundle.html (requires index.html in root)
Best Practices
- Start with Step 1 to initialize a clean project using scripts/init-artifact.sh.
- Follow the design guidelines to avoid AI slop (avoid excessive centered layouts, purple gradients, and Inter font).
- Develop within the generated src directory and leverage shadcn/ui components for consistency.
- Bundle after development with scripts/bundle-artifact.sh and ensure index.html exists in the root.
- Share bundle.html directly in Claude conversations and test it in a real chat context.
Example Use Cases
- A multi-step onboarding flow with internal routing and stateful steps.
- An interactive product catalog with filters and a shopping-like workflow.
- A dashboard-style artifact showcasing widgets arranged with Tailwind utilities.
- A help center with collapsible sections and nested components.
- A feature demo gallery that demonstrates transitions and component composition.
