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.
This skill MUST be used whenever the task involves UI development, renderer code changes, adding or modifying components, creating modals or dialogs, working with CSS styles, building new UI…
$ npx skills add elirantutia/vibeyard --skill ui-dev -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install elirantutia/vibeyard ui-dev --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/elirantutia/vibeyard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/ui-dev .claude/skills/ui-dev && 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 "ui-dev" agent skill from https://github.com/elirantutia/vibeyard/tree/main/.claude/skills/ui-dev into .claude/skills/ui-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-dev", 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/elirantutia/vibeyard/tree/main/.claude/skills/ui-devType 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 elirantutia/vibeyard --skill ui-dev -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install elirantutia/vibeyard ui-dev --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/elirantutia/vibeyard.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/ui-dev .agents/skills/ui-dev && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ui-dev" agent skill from https://github.com/elirantutia/vibeyard/tree/main/.claude/skills/ui-dev into .agents/skills/ui-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-dev", 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 elirantutia/vibeyard --skill ui-dev -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install elirantutia/vibeyard ui-dev --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/elirantutia/vibeyard.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/ui-dev .cursor/skills/ui-dev && 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 "ui-dev" agent skill from https://github.com/elirantutia/vibeyard/tree/main/.claude/skills/ui-dev into .cursor/skills/ui-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-dev", 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/elirantutia/vibeyard.git --path .claude/skills/ui-dev--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 elirantutia/vibeyard --skill ui-dev -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install elirantutia/vibeyard ui-dev --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/elirantutia/vibeyard.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/ui-dev .gemini/skills/ui-dev && 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 "ui-dev" agent skill from https://github.com/elirantutia/vibeyard/tree/main/.claude/skills/ui-dev into .gemini/skills/ui-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-dev", 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 elirantutia/vibeyard ui-devInstalls 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 elirantutia/vibeyard --skill ui-dev -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/elirantutia/vibeyard.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/ui-dev .github/skills/ui-dev && 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 "ui-dev" agent skill from https://github.com/elirantutia/vibeyard/tree/main/.claude/skills/ui-dev into .github/skills/ui-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-dev", 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 elirantutia/vibeyard --skill ui-dev -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install elirantutia/vibeyard ui-dev --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/elirantutia/vibeyard.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/ui-dev .opencode/skills/ui-dev && 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 "ui-dev" agent skill from https://github.com/elirantutia/vibeyard/tree/main/.claude/skills/ui-dev into .opencode/skills/ui-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-dev", 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.
ui-devThis skill MUST be used whenever the task involves UI development, renderer code changes, adding or modifying components, creating modals or dialogs, working with CSS styles, building new UI…
UI Dev is an agent skill from elirantutia/vibeyard. This skill MUST be used whenever the task involves UI development, renderer code changes, adding or modifying components, creating modals or dialogs, working with CSS styles, building new UI features, or touching any file in src/renderer/. Use this skill when the user asks to "add a button", "create a modal", "add a dropdown", "update the sidebar", "style a component", "add a new UI feature", or any renderer/frontend work.
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design. It works with TypeScript. The repository describes itself as: The IDE built for AI coding agents. The licence is MIT.
Read from SKILL.md and the folder at commit 19bc19f. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and css).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
UI Dev loads about 2.4k tokens when it runs. Until then it costs about 108 tokens; SKILL.md has 711 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.
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.
The full file from elirantutia/vibeyard at commit 19bc19f, republished under its MIT licence (© elirantutia). 711 words, ~2,350 tokens.
.claude/skills/ui-dev/SKILL.md (or your agent's skills folder).This project uses vanilla TypeScript DOM manipulation — no framework. All UI lives in src/renderer/. Follow the patterns and reuse the components documented below.
Never use native <select>. Always use the custom select component:
import { createCustomSelect } from './components/custom-select';
const select = createCustomSelect('my-select', [
{ value: 'a', label: 'Option A' },
{ value: 'b', label: 'Option B' },
{ value: 'c', label: 'Disabled', disabled: true },
], 'a'); // default value
// select.getValue() — get current value
// select.destroy() — cleanupsrc/renderer/components/custom-select.ts.custom-select, .custom-select-trigger, .custom-select-dropdown, .custom-select-itemUse showModal() for generic modals with form fields:
import { showModal, closeModal, setModalError } from './components/modal';
showModal('My Title', [
{ id: 'name', label: 'Name', type: 'text', placeholder: 'Enter name' },
{ id: 'option', label: 'Option', type: 'select', options: [...] },
{ id: 'enabled', label: 'Enable feature', type: 'checkbox' },
], (values) => {
// values is Record<string, string>
if (!values.name) {
setModalError('name', 'Name is required');
return;
}
// ... handle confirm
closeModal();
});src/renderer/components/modal.tsshowModal(), closeModal(), setModalError()text, checkbox, select (uses custom select internally)For specialized modals (complex layout, multi-pane, unique behavior), create a dedicated file in src/renderer/components/ following the existing pattern (e.g., preferences-modal.ts, usage-modal.ts).
For in-context alerts shown above the terminal:
import { showAlertBanner, removeAlertBanner } from './components/alert-banner';
showAlertBanner({
icon: '⚠️',
message: 'Something happened',
ctaLabel: 'Fix it',
onCta: () => { /* handle action */ },
dismissLabel: 'Dismiss',
onDismiss: () => { removeAlertBanner(); },
});src/renderer/components/alert-banner.ts.insight-alert, .insight-alert-icon, .insight-alert-message, .insight-alert-cta, .insight-alert-dismiss.insight-alert-info variant for informational (blue) alertsUse existing CSS classes — do not create new button styles:
| Class | Use for |
|---|---|
.btn-primary | Canonical primary/CTA button (accent fill, --accent-dim hover, --radius-md). Use for every solid-accent action. Defined in base.css. |
.btn-secondary | Canonical secondary button (bordered, neutral --bg-primary fill, --bg-hover hover, same --radius-md + size as primary, normal weight). Use for Cancel and every neutral action. Add .danger for destructive (red). Defined in base.css. |
.btn-sm / .btn-xs | Compact size modifiers — pair with .btn-primary or .btn-secondary. btn-sm for dense card/toolbar rows; btn-xs for tight github rows. Single-class so a context's geometry class still wins. |
.icon-btn | Small 26×26px icon buttons (tab bar, sidebar actions) |
.modal-field-btn | Inline button next to a modal field (e.g., "Browse") |
.config-section-add-btn | Add button in config sections |
A modal footer is .btn-secondary (Cancel) next to .btn-primary (Confirm) — they share size and corner radius so the pair lines up.
For split buttons (main + chevron), add .btn-primary/.btn-secondary plus the context's geometry-only class (e.g. .widget-github-fix-main, .team-card-chat-dropdown) which is defined later in source order so it correctly overrides the corner-radius/padding without redefining the fill. The same applies to structural-only classes kept on consolidated buttons (.team-card-btn, .widget-team-card-btn, .project-tab-toolbar-btn for its .active state, .share-btn for its .hidden toggle).
| Class | Use for |
|---|---|
.scope-badge.user / .scope-badge.project | Scope indicators |
.readiness-badge | Status badges |
.git-file-badge | Git status letter indicators |
.file-viewer-area-badge | Git area badges (staged, working, etc.) |
Never hardcode colors. Always use CSS variables from src/renderer/styles/base.css:
/* Backgrounds */
var(--bg-primary) /* #000000 — main background */
var(--bg-secondary) /* #0a0a0a — secondary background */
var(--bg-tertiary) /* #1a1a1a — tertiary / elevated surfaces */
var(--bg-hover) /* #222222 — hover state */
/* Text */
var(--text-primary) /* #e0e0e0 */
var(--text-secondary) /* #a0a0b0 */
var(--text-muted) /* #606070 */
/* Accents & borders */
var(--accent) /* #e94560 — primary accent (red) */
var(--accent-dim) /* #c73e55 */
var(--border) /* #333333 */
var(--bookmark) /* #e8a317 */Semantic status colors (these are not CSS variables — use the hex values directly):
var(--accent) with pulse animation#f4b400 (yellow)#34a853 (green)#e67e22 (orange)#4285f4 (blue)var(--text-muted).component-child pattern (e.g., .modal-field, .tab-status).active, .disabled, .hidden, .focused (e.g., .tab-item.active)4px standard, 2-3px small, 8px rounded/pills, 50% circular0.15s for hover/focus statesJetBrains Mono, Fira Code, etc.) for code/terminalvar(--border) thumb, 3px radius)Components use factory functions that return an instance object:
export function createMyComponent(id: string, options: Options): MyComponentInstance {
const el = document.createElement('div');
// ... build DOM ...
return {
element: el,
getValue() { /* ... */ },
destroy() { /* cleanup listeners, remove DOM */ },
};
}Use appState event emitter for reactive updates:
import { appState } from '../state';
appState.on('session-changed', (sessionId) => { /* update UI */ });Always provide a destroy() method that removes event listeners and DOM nodes. This prevents memory leaks when sessions/tabs are closed.
document.createElement() + property assignment over innerHTMLinnerHTML, always escape user content with esc() from src/renderer/components/dom-utils.tsclassList.toggle() / classList.add() / classList.remove() for conditional classeselement.dataset.* for data attributesComponents that re-render periodically (timers, event-driven updates) must check for active text selection before wiping the DOM. Destroying DOM nodes while the user is selecting text clears their selection. Guard re-renders like this:
const sel = window.getSelection();
if (sel && sel.rangeCount > 0 && !sel.isCollapsed && container.contains(sel.anchorNode)) {
return; // skip render — user is selecting text
}Also ensure clickable containers that hold selectable text use stopPropagation() on the text element to prevent click-to-select from triggering the parent's click handler, and set user-select: text; cursor: text; in CSS.
Add styles to the appropriate existing CSS file — do not create new CSS files unless introducing a wholly new component area:
| File | Contents |
|---|---|
styles/base.css | CSS variables, resets, global styles |
styles/modals.css | Modal, custom select, config sections, path autocomplete |
styles/tabs.css | Tab bar, icon buttons, context menus |
styles/sidebar.css | Sidebar, project list, update banner |
styles/terminal.css | Terminal pane, status bar, exit overlay |
styles/alerts.css | Alert banners, insight alerts, readiness badges |
styles/search.css | Search bar, toggle buttons, match highlighting |
styles/dialogs.css | Help dialog |
styles/preferences.css | Preferences modal, sections |
styles/session-history.css | Session history list |
styles/file-viewer.css | File viewer, diff display |
styles/git-panel.css | Git panel, worktree selector |
styles/mcp-inspector.css | MCP inspector pane |
styles/session-inspector.css | Session inspector panel |
© elirantutia, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/ui-dev of elirantutia/vibeyard.
Open the folder on GitHubat commit 19bc19f
UI Dev 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 |
|---|---|---|---|---|---|---|
| UI Dev this skillelirantutia/vibeyard | 1.4k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Web Artifacts Builderanthropics/skills | 180k | 41 repos | ~769 | Automated safety check: Pass | Apache-2.0 | |
| Ink Tui Wizardnovuhq/novu | 40k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Frontend Module Standardssiteboon/claudecodeui | 14k | — | ~2.6k | Automated safety check: Pass | AGPL-3.0 | |
| Dify Component Writing Guidelanggenius/dify | 158k | — | ~626 | Automated safety check: Pass | Custom licence | |
| React Frontend Development Guidelinesdiet103/claude-code-infrastructure-showcase | 10k | 2 repos | ~2.9k | Automated safety check: Pass | MIT |
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.
novuhq/novu
Build terminal user interfaces (TUIs) using Ink (React for CLIs) and @inkjs/ui with a reactive, session-driven wizard pattern.
siteboon/claudecodeui
Enforces one repository's React and TypeScript module layout for code under src/: source-root imports, feature barrels, deliberate exports and no deep imports.
langgenius/dify
Use when implementing or refactoring React/TypeScript components and the task requires decisions about component ownership, feature boundaries, state, data…
diet103/claude-code-infrastructure-showcase
Guidelines for React 18 and TypeScript apps covering Suspense data fetching, lazy loading, feature folders, MUI v7 styling, TanStack Router and performance.
ChrisWiles/claude-code-showcase
Shows how to build forms with Formik and Yup validation, including conditional rules, field helpers, GraphQL submission, edit forms and multi-step flows.
elirantutia/vibeyard
This skill MUST be used whenever the task involves adding, installing, or upgrading an npm package/library/dependency in this project.
Works with
Categories
This skill MUST be used whenever the task involves UI development, renderer code changes, adding or modifying components, creating modals or dialogs, working with CSS styles, building new UI…. UI Dev is an agent skill from elirantutia/vibeyard. This skill MUST be used whenever the task involves UI development, renderer code changes, adding or modifying components, creating modals or dialogs, working with CSS styles, building new UI features, or touching any file in src/renderer/.
UI Dev fits situations like: the user asks to add a button; update the sidebar; style a component; add a new UI feature.
Run `npx skills add elirantutia/vibeyard --skill ui-dev -a claude-code`. Or copy the skill folder (.claude/skills/ui-dev in elirantutia/vibeyard) into .claude/skills/ui-dev in your project. Claude Code loads it when a task matches its description.
Run `npx skills add elirantutia/vibeyard --skill ui-dev -a codex`. Or copy the skill folder (.claude/skills/ui-dev in elirantutia/vibeyard) into .agents/skills/ui-dev in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add elirantutia/vibeyard --skill ui-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ui-dev, .gemini/skills/ui-dev, .github/skills/ui-dev and .opencode/skills/ui-dev in your project.
SKILL.md names no scripts, command-line tools or credentials: UI Dev is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
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.
UI Dev is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.4k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with UI Dev: Web Artifacts Builder (anthropics/skills, 180k stars), Ink Tui Wizard (novuhq/novu, 40k stars), Frontend Module Standards (siteboon/claudecodeui, 14k stars) and Dify Component Writing Guide (langgenius/dify, 158k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
elirantutia (a GitHub user) maintains it in elirantutia/vibeyard, which has 1,387 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 3, 2026.
Source: elirantutia/vibeyard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.