artifacts-builder
Skill4 starsChanged 10 months agoMITView on GitHub
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.
63 other projects use a version of this, 9 of them edited.
Adopted by
Most recently taken up by
- BrightGold70/skillsword for word, first seen Nov 8, 2026
- Tejas9406/vibe-coding-osword for word, first seen Nov 1, 2026
- OpenSourceAssist/awesome-agent-skillsword for word, first seen Nov 1, 2026
- naman10parikh/pixeledited, first seen Oct 25, 2026
- davidanthonyn/claude-skillsedited, first seen Oct 20, 2026
- lin-jona/claude-skillsword for word, first seen Oct 15, 2026
Used with
Projects with it also use skill-share, raffle-winner-picker and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ArogyaReddySkillskill-share
A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.
Also in 20 projects that use this
ArogyaReddySkillraffle-winner-picker
Picks random winners from lists, spreadsheets, or Google Sheets for giveaways, raffles, and contests. Ensures fair, unbiased selection with transparency.
Also in 23 projects that use this
trendinuxSkilltwitter-algorithm-optimizer
Analyze and optimize tweets for maximum reach using Twitter's open-source algorithm insights. Rewrite and edit user tweets to improve engagement and visibility based on how the recommendation system ranks content.
Also in 12 projects that use this
guaderramaSkilllead-research-assistant
Identifies and qualifies potential leads by analyzing products/services, understanding ideal customer profiles, conducting intelligent web research using Bright Data MCP tools, and providing actionable outreach strategies. Use when researching leads, prospecting, qualifying contacts, analyzing companies, enriching lead data, or creating outreach campaigns.
Also in 25 projects that use this
- +6 more from ArogyaReddy
Other versions63 projects use a version of this.
Word for word · 50
- ComposioHQ/awesome-claude-skills★ 75k100% same
- Prat011/awesome-llm-skills★ 1.7k100% same
- maslennikov-ig/claude-code-orchestrator-kit★ 248100% same
- JayZeeDesign/awesome-claude-skills★ 169100% same
- ArogyaReddy/ComposioHQ-awesome-claude-skills★ 45100% same
- frostant/awesome-claude-skills★ 44100% same
- ttmouse/skills★ 34100% same
- ammosu/awesome-claude-skills-zh-TW★ 27100% same
- nilecui/SkillsBase★ 27100% same
- shajith003/awesome-claude-skills★ 25100% same
40 more not listed
Edited · 9
- Prorise-cool/Claude-Code-Multi-Agent★ 30413% same
- walidboulanouar/Ay-Skills★ 9082% same
- jhy0285/monofield★ 614% same
- Crumbgrabber/llm_system_template_agents_skills_patterns_tools_prompts★ 379% same
- jasonmichaelbell78-creator/sonash-v0★ 289% same
- pepebot-space/skills★ 298% same
- jpoindexter/theft-kit★ 114% same
- davidanthonyn/claude-skills★ 014% same
- naman10parikh/pixel★ 094% same
Wrote their own version · 4
- gonzaloraknarok88/CLAUDE-HABILIDADES★ 3same name
- sasanniroo/Claude_skills_zh-CN★ 3same name
- gauravv-g/claude-skills-collection★ 1same name
- bin1874/awesome-claude-skills-zh★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository71 other files it gives its agents.
- AGENTS.mdAGENTS.md
- algorithmic-artSkill
- architecture-diagram-creatorSkill
- brainstormingSkill
- brand-guidelinesSkill
- canvas-designSkill
- changelog-generatorSkill
- code-auditorSkill
- codebase-documenterSkill
- code-executionSkill
- code-refactorSkill
- code-transferSkill
- content-research-writerSkill
- conversation-analyzerSkill
- csv-data-summarizerSkill
- dashboard-creatorSkill
- dev-graph-exportsSkill
- dispatching-parallel-agentsSkill
- doc-coauthoringSkill
- docker-helperSkill
- docxSkill
- ensemble-solvingSkill
- executing-plansSkill
- feature-planningSkill
- file-operationsSkill
- file-organizerSkill
- finishing-a-development-branchSkill
- flowchart-creatorSkill
- frontend-designSkill
- git-pushingSkill
- image-enhancerSkill
- imagenSkill
- internal-commsSkill
- markitdownSkill
- mcp-builderSkill
- pdfSkill
- pixel-detective-exportsSkill
- pptxSkill
- project-bootstrapperSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- review-implementingSkill
- rituals-guideSkill
- systematic-debuggingSkill
- scientific-visualizationSkill
- skill-creatorSkill
- skills-summarizerSkill
- skills-updaterSkill
- slack-gif-creatorSkill
- sprint-perspectivesSkill
- sprint-summary-pdfSkill
- start-dev-graphSkill
- start-pixel-detectiveSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- tailored-resume-generatorSkill
- technical-doc-creatorSkill
- template-skillSkill
- test-driven-developmentSkill
- test-fixingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 1 is common, 0 are distinctive, and 0 are very specific to this project.
1
Common
Most of the 6 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 26
Run the initialization script to create a new React project:
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.shThis 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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

