Web Artifacts Builder
anthropics/skills
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
Install and configure the Zaidan component registry in an existing SolidJS codebase, and recommend Zaidan components for a product or interaction need.
Install Zaidan
$ npx skills add carere/zaidan --skill zaidan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install carere/zaidan zaidan --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/carere/zaidan.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/zaidan .claude/skills/zaidan && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "zaidan" agent skill from https://github.com/carere/zaidan/tree/main/.agents/skills/zaidan into .claude/skills/zaidan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zaidan", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/carere/zaidan/tree/main/.agents/skills/zaidanType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add carere/zaidan --skill zaidan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install carere/zaidan zaidan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/carere/zaidan.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/zaidan .agents/skills/zaidan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "zaidan" agent skill from https://github.com/carere/zaidan/tree/main/.agents/skills/zaidan into .agents/skills/zaidan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zaidan", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add carere/zaidan --skill zaidan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install carere/zaidan zaidan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/carere/zaidan.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/zaidan .cursor/skills/zaidan && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "zaidan" agent skill from https://github.com/carere/zaidan/tree/main/.agents/skills/zaidan into .cursor/skills/zaidan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zaidan", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/carere/zaidan.git --path .agents/skills/zaidan--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add carere/zaidan --skill zaidan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install carere/zaidan zaidan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/carere/zaidan.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/zaidan .gemini/skills/zaidan && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "zaidan" agent skill from https://github.com/carere/zaidan/tree/main/.agents/skills/zaidan into .gemini/skills/zaidan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zaidan", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install carere/zaidan zaidanInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add carere/zaidan --skill zaidan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/carere/zaidan.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/zaidan .github/skills/zaidan && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "zaidan" agent skill from https://github.com/carere/zaidan/tree/main/.agents/skills/zaidan into .github/skills/zaidan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zaidan", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add carere/zaidan --skill zaidan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install carere/zaidan zaidan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/carere/zaidan.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/zaidan .opencode/skills/zaidan && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "zaidan" agent skill from https://github.com/carere/zaidan/tree/main/.agents/skills/zaidan into .opencode/skills/zaidan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zaidan", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
zaidan- GitHub stars
- 147
- Used in
- 1 other repo
- Token cost
- ~1.4k tokens
- SKILL.md length
- 656 words
- Files
- 4 (incl. references)
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Install and configure the Zaidan component registry in an existing SolidJS codebase, and recommend Zaidan components for a product or interaction need.
- Works in 7 steps: Inspect package.json, the lockfile,… → Translate the user's request into… → Verify recommended item names against… → …
- Setting up Zaidan
- SKILL.md covers Load References, What the Registry Holds, Workflow and Recommendation Standard, plus 1 more section
- Reaches zaidan.carere.dev
What it does
Zaidan is an agent skill from carere/zaidan. Install and configure the Zaidan component registry in an existing SolidJS codebase, and recommend Zaidan components for a product or interaction need. Use when setting up Zaidan, adding Zaidan components, fixing consumer-side registry configuration, or deciding which Zaidan components to compose for a SolidJS interface.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `agents/openai.yaml`, `references/component-selection.md` and `references/installation.md`).
It sits in Frontend & Design. It works with shadcn/ui. The repository describes itself as: Shadcn registry for SolidJS. The licence is MIT.
When your agent uses it
- Setting up Zaidan
- Adding Zaidan components
- Fixing consumer-side registry configuration
- Deciding which Zaidan components to compose for a SolidJS interface
Example prompts
- “/zaidan”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Inspect package.json, the lockfile, framework configuration, TypeScript
- Translate the user's request into interaction needs. Recommend the smallest
- Verify recommended item names against the current registry before presenting
- Configure only missing prerequisites. Preserve the project's package
- Add the selected components through the configured @zaidan registry. Let
- Inspect the generated files and imports. Adapt the user's application only
- Run the smallest relevant formatting, typecheck, or build command available
What it can do on your machine
Read from SKILL.md and the folder at commit 271ffce. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
zaidan.carere.dev
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Zaidan loads about 1.4k tokens when it runs, and up to ~4.9k if it reads all its reference files. Until then it costs about 82 tokens; SKILL.md has 656 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from carere/zaidan at commit 271ffce, republished under its MIT licence (© carere). 656 words, ~1,440 tokens.
Download SKILL.mdSave it as
.claude/skills/zaidan/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- zaidan
- description
- Install and configure the Zaidan component registry in an existing SolidJS codebase, and recommend Zaidan components for a product or interaction need. Use when setting up Zaidan, adding Zaidan components, fixing consumer-side registry configuration, or deciding which Zaidan components to compose for a SolidJS interface.
Zaidan
Use this skill for consumer-side work in a SolidJS application. Treat Zaidan as a source-code registry: configure the project, select suitable components, add them with the registry CLI, and verify the resulting SolidJS code.
Use shadcn-to-zaidan instead when the task is to import, sync, transform, or
maintain a shadcn-style React component inside the Zaidan registry.
Load References
- Read
references/installation.mdbefore installing, configuring, adding, or troubleshooting Zaidan in a project. - Read
references/component-selection.mdwhen recommending components or deciding how to compose a requested interface.
What the Registry Holds
One @zaidan registry serves several kinds of item. Knowing which kind a name
is tells you what the CLI will write.
| Kind | Names | What lands in the project |
|---|---|---|
| Components | button, dialog, sidebar, … | Source files under the ui alias |
| Blocks | sortable, image-crop, message-scroller, questionnaire, and the chart examples (chart-bar-default, chart-line-interactive, …) | Larger compositions plus the components they use |
| Hook | use-mobile | Source file under the hooks alias |
| Shared component | color-mode | Source file under the components alias |
| Styles | style-vega, style-nova, style-maia, style-lyra, style-mira, style-luma, style-sera, style-rhea | styles/base.css and styles/utilities.css, plus their imports |
| Base colors and themes | neutral, stone, zinc, gray, mauve, olive, mist, taupe; blue, green, … | Light and dark CSS variables |
| Chart palettes | chart-blue, chart-neutral, … | chart-1 … chart-5 only |
| Radius | radius-none, radius-small, radius-medium, radius-large | --radius |
| Fonts | font-inter, font-geist-mono, … | The face, wired to --font-sans, --font-serif, or --font-mono |
| Typeset | typeset | styles/typeset.css and its import |
Two items are generated from a code rather than listed in the registry:
@zaidan/preset-<code>— a whole design system (style, base color, theme, chart palette, fonts, radius, menu accent) from a code produced byhttps://zaidan.carere.dev/create.@zaidan/typeset-<code>— the typeset stylesheet, the fonts a design uses, and its.typeset-<item>preset class, from a code produced byhttps://zaidan.carere.dev/typeset.
Both resolve over the CLI even though no listing entry exists for them. Prefer a preset over a hand-assembled list of style, color, radius, and font items when the user wants a full design system.
Show full SKILL.md (343 more words)Show less
Workflow
- Inspect
package.json, the lockfile, framework configuration, TypeScript aliases, global CSS, andcomponents.jsonwhen present. Identify the SolidJS framework, package manager, Tailwind version, existing aliases, and current Zaidan style before editing. - Translate the user's request into interaction needs. Recommend the smallest
useful component set and explain the role of each component. Distinguish
alternatives such as
selectversuscombobox,dialogversusalert-dialog, andsheetversusdrawer. - Verify recommended item names against the current registry before presenting
an install command. In this repository, inspect
src/registry/kobalte/registry.json; elsewhere, resolve the correspondinghttps://zaidan.carere.dev/r/kobalte/<name>.jsonitem.@zaidan/preset-<code>and@zaidan/typeset-<code>are the exception: they are generated on demand from the code, so they resolve without appearing in the registry listing. - Configure only missing prerequisites. Preserve the project's package
manager, framework conventions, aliases, CSS entry point, theme choices, and
existing
components.jsonvalues. - Add the selected components through the configured
@zaidanregistry. Let registry metadata install transitive Zaidan items and npm dependencies. - Inspect the generated files and imports. Adapt the user's application only when requested; installing components alone does not imply building a feature with them.
- Run the smallest relevant formatting, typecheck, or build command available in the target project. Report the configuration changed, components added, commands run, and any remaining integration work.
Recommendation Standard
Base recommendations on behavior, not visual resemblance alone. Account for:
- the information or action the interface must expose;
- whether content is persistent, contextual, modal, or transient;
- keyboard, focus, dismissal, and validation behavior;
- data size, search needs, touch use, and responsive layout;
- existing components already installed in the project.
Lead with one recommended composition. Mention an alternative only when a real product decision changes the choice. State when Zaidan supplies primitives but the requested product pattern still needs application-owned state, data loading, validation, or layout.
Boundaries
- Keep generated components as editable application source; do not add a
runtime
zaidanpackage. - Use SolidJS imports and syntax in consumer examples.
- Prefer the registry CLI over copying source files by hand.
- Keep registry-authoring, React-to-Solid transformation, release syncing,
Zaidan documentation, and registry manifest maintenance in
shadcn-to-zaidan.
© carere, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in .agents/skills/zaidan of carere/zaidan.
- SKILL.md
- agents/openai.yaml
- references/component-selection.md
- references/installation.md
Open the folder on GitHubat commit 271ffce
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in carere/zaidan, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Zaidan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Zaidan this skillcarere/zaidan | 147 | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Web Artifacts Builderanthropics/skills | 180k | 40 repos | ~769 | Automated safety check: Pass | Apache-2.0 | |
| UI StylingOhh-889/skyroc | 795 | 13 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Shadcnsupabase/evals | 145 | 43 repos | ~4.5k | Automated safety check: Pass | Apache-2.0 | |
| Integrating shadcn/ui Componentsgoogle-labs-code/stitch-skills | 8.5k | 4 repos | ~2.3k | Automated safety check: Notes | Apache-2.0 | |
| UI UX Pro Maxsaoudi-h/solar-icons | 190 | 18 repos | ~11k | Automated safety check: Notes | Custom licence |
Similar skills
- Official
UI Styling
Ohh-889/skyroc
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs.
- Official
Shadcn
supabase/evals
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI.
- Official
Integrating shadcn/ui Components
google-labs-code/stitch-skills
Guides finding, installing, customizing and wiring up shadcn/ui components in a project, with MCP tools for the component catalog and registries.
UI UX Pro Max
saoudi-h/solar-icons
UI/UX design intelligence for web and mobile. An agent skill from saoudi-h/solar-icons.
Creative Tim UI Blocks
creativetimofficial/ui
Helps install, generate and review Creative Tim UI blocks: shadcn/ui-based React and Tailwind sections that follow a restrained, production-minded design philosophy.
More from carere/zaidan
React To Solid
carere/zaidan
React-to-SolidJS transformation patterns for porting shadcn-style React components, examples, docs snippets, and blocks into Zaidan.
Shadcn To Zaidan
carere/zaidan
Port and sync shadcn-style React components, blocks, examples, and documentation into Zaidan.
Related
Works with
Categories
Questions about Zaidan
What does Zaidan do?
Install and configure the Zaidan component registry in an existing SolidJS codebase, and recommend Zaidan components for a product or interaction need. Zaidan is an agent skill from carere/zaidan. Install and configure the Zaidan component registry in an existing SolidJS codebase, and recommend Zaidan components for a product or interaction need.
When should I use Zaidan?
Zaidan fits situations like: setting up Zaidan; adding Zaidan components; fixing consumer-side registry configuration; deciding which Zaidan components to compose for a SolidJS interface.
How do I install Zaidan in Claude Code?
Run `npx skills add carere/zaidan --skill zaidan -a claude-code`. Or copy the skill folder (.agents/skills/zaidan in carere/zaidan) into .claude/skills/zaidan in your project. Claude Code loads it when a task matches its description.
How do I install Zaidan in Codex?
Run `npx skills add carere/zaidan --skill zaidan -a codex`. Or copy the skill folder (.agents/skills/zaidan in carere/zaidan) into .agents/skills/zaidan in your project. Codex loads it when a task matches its description.
Can I use Zaidan in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add carere/zaidan --skill zaidan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/zaidan, .gemini/skills/zaidan, .github/skills/zaidan and .opencode/skills/zaidan in your project.
What does Zaidan need to run?
SKILL.md names no scripts, command-line tools or credentials: Zaidan is instructions for the agent only.
Does Zaidan access the network?
SKILL.md names 1 domain. In commands or code: zaidan.carere.dev; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Zaidan safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Zaidan use?
Zaidan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Zaidan use?
About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.4k tokens, read only when the agent opens those files.
What are the alternatives to Zaidan?
Skills that share tags, products or a category with Zaidan: Web Artifacts Builder (anthropics/skills, 180k stars), UI Styling (Ohh-889/skyroc, 795 stars), Shadcn (supabase/evals, 145 stars) and Integrating shadcn/ui Components (google-labs-code/stitch-skills, 8.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Zaidan?
carere (a GitHub user) maintains it in carere/zaidan, which has 147 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 5, 2026.
Source: carere/zaidan on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.