Automated summary
This skill provides a toolset for building elaborate, multi-component claude.ai HTML artifacts with React, Tailwind CSS and shadcn/ui, then bundling them into a single self-contained HTML file.
Strengths
- Automates scaffolding of a React/TypeScript/Vite project with Tailwind and 40+ pre-installed shadcn/ui components
- The bundling script outputs one self-contained HTML file that can be shared directly as an artifact
- Includes explicit design guidance to steer away from typical AI-generated visual clichés
Limitations
- Only targets complex artifacts; simple single-file HTML/JSX work does not need it
- Relies on bash scripts, Node 18+ and several npm dependencies for init and bundling
- License terms are deferred to an external LICENSE.txt not detailed in the SKILL.md
Use it when a claude.ai artifact needs state management, routing or shadcn/ui components inside a structured React project.
Avoid it for a simple single-file HTML/JSX artifact, where the init-and-bundle workflow would be overkill.
Security analysis
CautionThe skill is a legitimate frontend artifact builder, but it relies on executing unreviewed local shell scripts and installing/building third-party npm dependencies. This is a normal but powerful development workflow, so it warrants caution rather than safe.
- •Instructs running project-local shell scripts (scripts/init-artifact.sh, scripts/bundle-artifact.sh) that are not included for review.
- •Causes package installation and bundling via npm/Parcel, which requires network access and executes third-party dependencies.
- •No destructive commands, secret exfiltration, obfuscated payloads, or safety-disabling instructions observed.
Examples
Crée un artefact claude.ai pour un tableau de bord de suivi de projets avec plusieurs onglets (vue d'ensemble, tâches, équipe), de la navigation et des composants shadcn/ui, puis bundle-le en un seul fichier HTML.Build a multi-page expense tracker artifact using React and shadcn/ui with a form to add expenses, a filtered list view, and summary stats, and bundle it into a single HTML file.name: web-artifacts-builder description: Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts. license: Complete terms in LICENSE.txt
Web Artifacts 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
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/web-artifacts-builder-mrwakggz/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/web-artifacts-builder-mrwakggz' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/web-artifacts-builder-mrwakggz/download' --output '.skill-downloads/web-artifacts-builder-mrwakggz/SKILL.md.part' && mv '.skill-downloads/web-artifacts-builder-mrwakggz/SKILL.md.part' '.skill-downloads/web-artifacts-builder-mrwakggz/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/web-artifacts-builder-mrwakggz/SKILL.md' && test -s '.skill-downloads/web-artifacts-builder-mrwakggz/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/web-artifacts-builder' && cp -R '.skill-downloads/web-artifacts-builder-mrwakggz' '.claude/skills/web-artifacts-builder'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/web-artifacts-builder-mrwakggz'openskills read 'web-artifacts-builder-mrwakggz'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/web-artifacts-builder-mrwakggz/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.