Skip to content
Development
Skill

/ui-dev

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

From plugin
vibeyard
1.4k2 skills3 commands

Claude Code

$ npx -y skills add elirantutia/vibeyard --skill ui-dev --agent claude-code

SKILL.md

ui-dev.SKILL.md
name: ui-dev
description: 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.

UI Development Guide

This project uses **vanilla TypeScript DOM manipulation** — no framework. All UI lives in `src/renderer/`. Follow the patterns and reuse the components documented below.

Custom Dropdown / Select

**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() — cleanup
  • **File**: `src/renderer/components/custom-select.ts`
  • **CSS classes**: `.custom-select`, `.custom-select-trigger`, `.custom-select-dropdown`, `.custom-select-item`
  • Supports keyboard navigation (Arrow keys, Enter, Escape, Tab)

Modals

Use `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();
});
  • **File**: `src/renderer/components/modal.ts`
  • Exports: `showModal()`, `closeModal()`, `setModalError()`
  • Supports field types: `text`, `checkbox`, `select` (uses custom select internally)
  • Supports field buttons (e.g., a "Browse" button next to a text input)
  • Keyboard: Enter to confirm, Escape to cancel

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`).

Alert Banners

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(); },
});
  • **File**: `src/renderer/components/alert-banner.ts`
  • **CSS classes**: `.insight-alert`, `.insight-alert-icon`, `.insight-alert-message`, `.insight-alert-cta`, `.insight-alert-dismiss`
  • Use `.insight-alert-info` variant for informational (blue) alerts

Buttons

Use 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).

Badges

| 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.) |

CSS Theming

**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):

  • Working/Active: `var(--accent)` with pulse animation
  • Waiting: `#f4b400` (yellow)
  • Completed/Success: `#34a853` (green)
  • Input: `#e67e22` (orange)
  • Info: `#4285f4` (blue)
  • Idle: `var(--text-muted)`

Styling Conventions

  • **Class naming**: `.component-c
Read more
@elirantutia
Ships withvibeyard

The IDE built for AI coding agents.

Stars on GitHub

Momentum

stars in total
1.4k
Star history of elirantutia/vibeyard on GitHub, a chart by star-history.com

Other skills on vibeyard.

add-npm-dependency

add-npm-dependency

This skill MUST be used whenever the task involves adding, installing, or upgrading an npm package/library/dependency in this…

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills12d309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc13d293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react2d252k
@facebook@facebookInstall Skill

Questions about ui-dev.

Which coding agents can use ui-dev?
ui-dev installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.