ClaudeSkills
Browse documentation

Source reviewed8a1541c4a3ff

Web Artifacts Builder - Claude의 React 아티팩트 스킬

Web Artifacts Builder 스킬이 React와 Tailwind를 shadcn 컴포넌트가 포함된 단일 HTML 아티팩트로 묶는 과정을 완전 해설.

Anthropic · Web Artifacts Builder

Existing editorial guidance is preserved. The current pinned official reference is separately labelled in English; translated editorial is not a new translation of the full source.

This is the existing editorial translation. The latest full official reference, where available, is provided separately in English.

The navigation uses English labels. Article languages are shown separately; the interface is not a full translation of the documentation.

Source text is documentation. These workflows have not been executed or tested by this site.

Skill and installationView sourceLicense
On this page

개요

공식 설명: "Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using React, Tailwind CSS, shadcn/ui. For complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file artifacts."

적용 범위에 주의: 단순한 단일 파일 아티팩트에는 이 스킬이 필요 없습니다. 프로젝트가 JSX 블록 하나에 담기지 않게 되는 순간을 위한 스킬입니다.

이 스킬의 작동 방식

SKILL.md는 디자인 가이드라인을 두른 5단계 파이프라인입니다:

  1. 초기화: scripts/init-artifact.sh로 React + Tailwind + shadcn/ui 사전 구성 워크스페이스 생성
  2. 개발: 실제 컴포넌트, 상태 관리, 라우팅으로 구현
  3. 번들: scripts/bundle-artifact.sh로 전체를 HTML 파일 하나로
  4. 공유: 아티팩트를 사용자에게 전달
  5. 테스트/시각화 (선택적 검증 단계)

shadcn-components.tar.gz가 동봉되어 네트워크 없이도 컴포넌트를 설치할 수 있습니다.

스킬 폴더 구성

  • scripts/init-artifact.sh - 프로젝트 스캐폴딩
  • scripts/bundle-artifact.sh - 단일 파일 HTML 번들러
  • scripts/shadcn-components.tar.gz - 오프라인 컴포넌트 라이브러리
  • SKILL.md, LICENSE.txt

나만의 스킬을 만들 때 배울 점

  • 실행 가능한 스크립트가 설명서를 이깁니다: 셋업을 산문으로 쓰는 대신 Claude가 실행할 셸 스크립트를 제공합니다.
  • 오프라인 의존성 동봉(shadcn 아카이브)은 샌드박스 환경에서도 스킬이 돌아가게 합니다 - 커뮤니티 스킬 대부분이 놓치는 디테일입니다.

GitHub에서 보기

skills/web-artifacts-builder

Current official reference · English8a1541c4a3ff

The original English source comes from the pinned version above. It is shown as inert documentation. Related scripts and resources remain in the upstream repository; this text is not a complete installation package.

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