OfficialProgramación y desarrollogithub.com

web-artifacts-builder

Conjunto de herramientas para crear artefactos HTML elaborados y de múltiples componentes para claude.ai, utilizando tecnologías web modernas (React, Tailwind CSS, shadcn/ui). Útil para artefactos complejos que requieren gestión de estado, enrutamiento o componentes de shadcn/ui, no para artefactos HTML/JSX simples de un solo archivo.

¿Qué es web-artifacts-builder?

Web Artifacts Builder es un conjunto de herramientas diseñado para facilitar la creación de artefactos HTML complejos y de múltiples componentes en claude.ai. A diferencia de los artefactos simples de un solo archivo, este sistema permite aprovechar tecnologías modernas como React 18, TypeScript, Vite, Parcel, Tailwind CSS y shadcn/ui para construir interfaces de usuario dinámicas y ricas en funcionalidad. El flujo de trabajo consta de cinco pasos: inicializar un proyecto con un script, desarrollar el artefacto editando el código generado, empaquetar todo en un único archivo HTML, compartirlo con el usuario y, opcionalmente, probarlo. Es especialmente útil para proyectos que requieren gestión de estado, enrutamiento o componentes de shadcn/ui, evitando el llamado 'AI slop' mediante pautas de diseño que desaconsejan el uso excesivo de diseños centrados, degradados púrpura, esquinas redondeadas uniformes y la fuente Inter. Compatible con Node 18+ y disponible como skill para Claude Code, Cursor y Codex.

Compatible con✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/anthropics/skills/tree/main/skills/web-artifacts-builder

Installed? Explore more Programación y desarrollo skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

Documentación

Web Artifacts Builder

Para construir artefactos frontend potentes para claude.ai, sigue estos pasos:

  1. Inicializa el repositorio frontend usando scripts/init-artifact.sh
  2. Desarrolla tu artefacto editando el código generado
  3. Empaqueta todo el código en un único archivo HTML usando scripts/bundle-artifact.sh
  4. Muestra el artefacto al usuario
  5. (Opcional) Prueba el artefacto

Stack: React 18 + TypeScript + Vite + Parcel (empaquetado) + Tailwind CSS + shadcn/ui

Pautas de diseño y estilo

MUY IMPORTANTE: Para evitar lo que a menudo se conoce como "AI slop", evita el uso excesivo de diseños centrados, degradados púrpura, esquinas redondeadas uniformes y la fuente Inter.

Inicio rápido

Paso 1: Inicializar el proyecto

Ejecuta el script de inicialización para crear un nuevo proyecto React:

bash scripts/init-artifact.sh <project-name>
cd <project-name>

Esto crea un proyecto completamente configurado con:

  • ✅ React + TypeScript (a través de Vite)
  • ✅ Tailwind CSS 3.4.1 con sistema de temas shadcn/ui
  • ✅ Alias de ruta (@/) configurados
  • ✅ Más de 40 componentes shadcn/ui preinstalados
  • ✅ Todas las dependencias de Radix UI incluidas
  • ✅ Parcel configurado para empaquetado (a través de .parcelrc)
  • ✅ Compatibilidad con Node 18+ (detecta automáticamente y fija la versión de Vite)

Paso 2: Desarrolla tu artefacto

Para construir el artefacto, edita los archivos generados. Consulta Tareas comunes de desarrollo más abajo para obtener orientación.

Paso 3: Empaquetar en un único archivo HTML

Para empaquetar la aplicación React en un único artefacto HTML:

bash scripts/bundle-artifact.sh

Esto crea bundle.html - un artefacto autónomo con todo el JavaScript, CSS y dependencias incrustadas. Este archivo se puede compartir directamente en conversaciones de Claude como artefacto.

Requisitos: Tu proyecto debe tener un index.html en el directorio raíz.

Lo que hace el script:

  • Instala dependencias de empaquetado (parcel, @parcel/config-default, parcel-resolver-tspaths, html-inline)
  • Crea la configuración .parcelrc con soporte para alias de ruta
  • Compila con Parcel (sin mapas de origen)
  • Incrusta todos los activos en un único HTML usando html-inline

Paso 4: Comparte el artefacto con el usuario

Finalmente, comparte el archivo HTML empaquetado en la conversación con el usuario para que pueda verlo como artefacto.

Paso 5: Probar/Visualizar el artefacto (Opcional)

Nota: Este es un paso completamente opcional. Realízalo solo si es necesario o si se solicita.

Para probar/visualizar el artefacto, utiliza las herramientas disponibles (incluyendo otras Skills o herramientas integradas como Playwright o Puppeteer). En general, evita probar el artefacto de antemano, ya que añade latencia entre la solicitud y el momento en que se puede ver el artefacto terminado. Prueba después, después de presentar el artefacto, si se solicita o si surgen problemas.

Referencia

Individual skills in this repo

This repo contains 19 individual skills — each has its own dedicated page.

academy-guide

Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

algorithmic-art

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists

anthropics/template-skill

Replace with description of the skill and when Claude should use it.

brand-guidelines

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

canvas-design

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists

claude-api

|-

discernment-nudge

After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

doc-coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of

frontend-design

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

internal-comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

mcp-builder

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

pdf

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

pptx

Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions \

skill-creator

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill

slack-gif-creator

Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like

theme-factory

Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

xlsx

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like \

Skills relacionados