seaworld008/web-artifacts-builder

Web Artifacts Builder

To build powerful frontend claude.ai artifacts, follow these steps:

1. Initialize the frontend repo using scripts/init-artifact.sh
2. Develop your artifact by editing the generated code
3. Bundle all code into a single HTML file using scripts/bundle-artifact.sh
4. Display artifact to user
5. (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 .parcelrc config 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

Artifact Quality Checklist

Before handing off the final HTML artifact, verify these points:

• The artifact opens without a build server and does not depend on local-only file paths.
• Core interactions work from the bundled bundle.html, not only during Vite development.
• Responsive layout has been considered for mobile, tablet, and desktop widths.
• State is initialized deterministically so the first render is useful without user setup.
• Any imported assets are embedded, copied, or replaced with stable remote URLs.
• The visual language is intentional; avoid default Tailwind spacing and generic component stacks when the user asks for design polish.

Common Failure Modes

• Missing path alias support: rerun the bundling script and confirm .parcelrc contains the resolver configuration.
• Oversized bundle: remove unused component imports, large image assets, and debug-only dependencies.
• Broken shadcn styles: confirm generated components import from the expected @/components/ui/* paths.
• Hydration-like mismatch: avoid relying on Date.now(), random values, or browser-only APIs during first render unless guarded.

Delivery Notes

When the user only asked for a quick static page, do not force this full React artifact workflow. Use it when complexity justifies the setup: multi-screen state, component libraries, rich interactions, or a reusable artifact that benefits from a local build loop.