| name | web-artifacts-builder |
| description | Suite of tools for creating elaborate, multi-component single-file HTML artifacts for chat or browser use 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 |
Codex Compatibility Notes
This skill was adapted from Anthropic's Claude Code skills so it can be used by Codex. Apply these interpretation rules while following the original instructions:
- Treat references to "Claude", "the next Claude", or "Reader Claude" as Codex or the current assistant unless the text is explicitly about Anthropic's Claude product or API.
- Treat "Claude Code" as Codex, and treat "Claude.ai" / "Claude app" as the current chat environment when that wording is only about where a workflow or artifact runs.
- Replace
AskUserQuestion with a concise direct question to the user.
- Replace
WebFetch / WebSearch with Codex web browsing tools.
- Replace
create_file with creating a normal workspace file, and replace str_replace / Edit with precise file edits using Codex's editing workflow.
- Only use subagents or delegation when the current environment supports it and the user has explicitly allowed that mode of work.
- If the skill discusses Anthropic, Claude API, or Anthropic branding as part of the user task, keep that product-specific content intact; only adapt the runtime and tool assumptions.
Web Artifacts Builder
To build powerful frontend HTML 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 opened directly in a browser or shared as a single HTML 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
