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."

適用範囲に注意：単純な1ファイルのアーティファクトにこのスキルは不要です。プロジェクトが単一の 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