Agent skill

UI Components

UI Component Development Guide for Kaiden. An agent skill from openkaiden/kaiden.

Apache-2.0Auto-check passedFrontend & Design

Install UI Components

skills CLI

$ npx skills add openkaiden/kaiden --skill ui-components -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install openkaiden/kaiden ui-components --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/openkaiden/kaiden.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/ui-components .claude/skills/ui-components && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "ui-components" agent skill from https://github.com/openkaiden/kaiden/tree/main/.agents/skills/ui-components into .claude/skills/ui-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-components", 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

$skill-installer install https://github.com/openkaiden/kaiden/tree/main/.agents/skills/ui-components

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

skills CLI

$ npx skills add openkaiden/kaiden --skill ui-components -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install openkaiden/kaiden ui-components --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/openkaiden/kaiden.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/ui-components .agents/skills/ui-components && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "ui-components" agent skill from https://github.com/openkaiden/kaiden/tree/main/.agents/skills/ui-components into .agents/skills/ui-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-components", 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.

skills CLI

$ npx skills add openkaiden/kaiden --skill ui-components -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install openkaiden/kaiden ui-components --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/openkaiden/kaiden.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/ui-components .cursor/skills/ui-components && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "ui-components" agent skill from https://github.com/openkaiden/kaiden/tree/main/.agents/skills/ui-components into .cursor/skills/ui-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-components", 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

$ gemini skills install https://github.com/openkaiden/kaiden.git --path .agents/skills/ui-components

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add openkaiden/kaiden --skill ui-components -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install openkaiden/kaiden ui-components --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/openkaiden/kaiden.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/ui-components .gemini/skills/ui-components && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "ui-components" agent skill from https://github.com/openkaiden/kaiden/tree/main/.agents/skills/ui-components into .gemini/skills/ui-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-components", 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.

GitHub CLI

$ gh skill install openkaiden/kaiden ui-components

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

skills CLI

$ npx skills add openkaiden/kaiden --skill ui-components -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/openkaiden/kaiden.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/ui-components .github/skills/ui-components && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "ui-components" agent skill from https://github.com/openkaiden/kaiden/tree/main/.agents/skills/ui-components into .github/skills/ui-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-components", 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.

skills CLI

$ npx skills add openkaiden/kaiden --skill ui-components -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install openkaiden/kaiden ui-components --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/openkaiden/kaiden.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/ui-components .opencode/skills/ui-components && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "ui-components" agent skill from https://github.com/openkaiden/kaiden/tree/main/.agents/skills/ui-components into .opencode/skills/ui-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-components", 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: ui-components
GitHub stars: 110
Token cost: ~2.1k tokens
SKILL.md length: 530 words
Files: 1
Skills in repo: 3
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

UI Component Development Guide for Kaiden. An agent skill from openkaiden/kaiden.

Works in 4 steps: Check @podman-desktop/ui-svelte before… → Never use Tailwind colors directly → Use the Icon component for all icons → …
Tasks that involve Design systems
SKILL.md covers Core Rules and How the Color Registry Works
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

UI Components is an agent skill from openkaiden/kaiden. UI Component Development Guide for Kaiden

Its SKILL.md is about 2.1k 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, covering Design systems. It works with Svelte. The licence is Apache-2.0.

When your agent uses it

Tasks that involve Design systems

Example prompts

“/ui-components”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Check @podman-desktop/ui-svelte before building from scratch
Never use Tailwind colors directly
Use the Icon component for all icons
Reuse existing Kortex Svelte components

What it can do on your machine

Read from SKILL.md and the folder at commit f34ac2f. 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 (its code samples are svelte).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

UI Components loads about 2.1k tokens when it runs. Until then it costs about 14 tokens; SKILL.md has 530 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~14
When it runs · the whole SKILL.md, loaded when a task matches: ~2.1k

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 openkaiden/kaiden at commit f34ac2f, republished under its Apache-2.0 licence (© openkaiden). 530 words, ~2,097 tokens.

Download SKILL.mdSave it as .claude/skills/ui-components/SKILL.md (or your agent's skills folder).

name: ui-components
description: UI Component Development Guide for Kaiden

UI Component Development Guide for Kaiden

Core Rules

1. Check `@podman-desktop/ui-svelte` before building from scratch

Before creating any new UI component, always check @podman-desktop/ui-svelte first. This is the shared component library that Kortex builds on. Only build custom components when nothing in this library fits.

Available components from @podman-desktop/ui-svelte:

Component	Purpose
`Button`, `CloseButton`, `Expandable`	Button variants
`Input`, `NumberInput`, `SearchInput`	Form inputs
`Checkbox`	Checkboxes
`Dropdown`, `DropdownMenu`	Selection menus
`Table`, `TableColumn`, `TableRow`, `TableSimpleColumn`, `TableDurationColumn`	Data tables
`DetailsPage`, `FormPage`, `NavPage`, `Page`	Page layouts
`Modal`	Modal dialogs
`Tab`	Tab navigation
`Tooltip`	Tooltips
`Link`	Styled links
`Spinner`, `LinearProgress`	Loading indicators
`StatusIcon`	Status indicators
`EmptyScreen`, `FilteredEmptyScreen`	Empty state views
`ErrorMessage`	Error alerts
`Carousel`	Carousel
`ListOrganizer`	List management
`SettingsNavItem`	Settings navigation

Icons are available from @podman-desktop/ui-svelte/icons (see rule 3 below).

Priority order when building UI:

Use a component from @podman-desktop/ui-svelte
Use an existing Kortex shared component (see rule 4)
Extend an existing component if close but not quite right
Only build from scratch as a last resort

2. Never use Tailwind colors directly

Never use raw Tailwind color classes like bg-red-500, text-gray-700, border-blue-300, etc.

Always use CSS variables from the color-registry so that values can be tuned by themes (light/dark mode and custom themes).

Format: [var(--pd-<color-name>)]

svelte

<!-- WRONG -->
<div class="bg-gray-800 text-white border-purple-500">...</div>

<!-- CORRECT -->
<div class="bg-[var(--pd-content-bg)] text-[var(--pd-content-text)] border-[var(--pd-content-divider)]">...</div>

Non-color Tailwind utilities (layout, spacing, sizing, typography, borders, effects) are fine.

3. Use the Icon component for all icons

Use the Icon component from @podman-desktop/ui-svelte/icons instead of inline SVGs, custom icon wrappers, or direct <Fa> usage.

svelte

<script lang="ts">
import { Icon } from '@podman-desktop/ui-svelte/icons';
import { faGear } from '@fortawesome/free-solid-svg-icons';
</script>

<!-- CORRECT -->
<Icon icon={faGear} size="xs" />

<!-- WRONG: inline SVG -->
<svg viewBox="0 0 512 512"><path d="M..."/></svg>

<!-- WRONG: direct Fa usage -->
<Fa icon={faGear} />

The Icon component supports:

FontAwesome IconDefinition objects (via <Fa> internally)
Font class icon strings (fas fa-*, far fa-*, fab fa-*, or -icon suffix)
Data URI images (strings starting with data:image/)
Svelte Components

Show full SKILL.md (259 more words)Show less

4. Reuse existing Kortex Svelte components

If @podman-desktop/ui-svelte doesn't have what you need, check Kortex's own shared components before building from scratch:

Primary shared component locations:

packages/renderer/src/lib/ui/ — Core UI components (~50 components)
packages/renderer/src/lib/button/ — Button components
packages/renderer/src/lib/table/ — Table components
packages/renderer/src/lib/modal/ — Modal dialogs
packages/renderer/src/lib/forms/ — Form components
packages/renderer/src/lib/dialogs/ — Dialog components
packages/renderer/src/lib/appearance/ — Theme/appearance components

Key reusable components include:

Component	File	Purpose
`Badge`	`lib/ui/Badge.svelte`	Status badges and labels
`Button`	`lib/button/Button.svelte`	Standard buttons
`DetailsPage`	`lib/ui/DetailsPage.svelte`	Detail view layouts
`FormPage`	`lib/ui/FormPage.svelte`	Form page layouts
`Label`	`lib/ui/Label.svelte`	Form labels
`SlideToggle`	`lib/ui/SlideToggle.svelte`	Toggle switches
`Typeahead`	`lib/ui/Typeahead.svelte`	Autocomplete inputs
`StatusDot`	`lib/ui/StatusDot.svelte`	Status indicators
`Steps`	`lib/ui/Steps.svelte`	Step-by-step wizards
`WarningMessage`	`lib/ui/WarningMessage.svelte`	Warning banners
`FileInput`	`lib/ui/FileInput.svelte`	File upload inputs
`PasswordInput`	`lib/ui/PasswordInput.svelte`	Password fields
`CopyToClipboard`	`lib/ui/CopyToClipboard.svelte`	Clipboard copy functionality

Always search for existing components before creating new ones. If an existing component is close but not quite right, prefer extending it over duplicating it.

How the Color Registry Works

Colors are defined in packages/main/src/plugin/color-registry.ts in the initColors() method, organized by category.

Finding the right color variable

Open packages/main/src/plugin/color-registry.ts
Find the appropriate category in initColors() (e.g. initButton(), initInput(), initTable())
Each category has a prefix constant (e.g. const button = 'button-';)
The CSS variable name is --pd- + prefix + specific name

Common color categories and prefixes

Category	Prefix	Example variable	Usage
Content	`content-`	`--pd-content-bg`	Page backgrounds, text
Button	`button-`	`--pd-button-primary-bg`	Button colors
Input	`input-field-`	`--pd-input-field-bg`	Form input colors
Table	`table-`	`--pd-table-header-bg`	Table styling
Modal	`modal-`	`--pd-modal-bg`	Modal dialogs
Card	`card-`	`--pd-card-bg`	Card components
Tab	`tab-`	`--pd-tab-active-bg`	Tab navigation
Status	`status-`	`--pd-status-running`	Status indicators
Navigation	`global-nav-`	`--pd-global-nav-bg`	Navigation bars

Example: Styling a new component

svelte

<script lang="ts">
  import { Button } from '@podman-desktop/ui-svelte';
  import { Icon } from '@podman-desktop/ui-svelte/icons';
  import { faPlus } from '@fortawesome/free-solid-svg-icons';
</script>

<div class="bg-[var(--pd-content-bg)] text-[var(--pd-content-text)] p-4 rounded-lg">
  <h2 class="text-[var(--pd-content-header)]">Title</h2>
  <p class="text-[var(--pd-content-text)]">Description</p>

  <Button on:click={handleAction}>
    <Icon icon={faPlus} size="xs" />
    Add Item
  </Button>
</div>

Files

Just SKILL.md in .agents/skills/ui-components of openkaiden/kaiden.

Open the folder on GitHubat commit f34ac2f

Compare with similar skills

UI Components 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.

UI Components compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
UI Components this skillopenkaiden/kaiden	110	—	~2.1k	Automated safety check: Pass	Apache-2.0	today
UI/UX Design System AdvisorGalaxy-Dawn/claude-scholar	5.7k	1 repos	~1.1k	Automated safety check: Pass	MIT	14 days ago
Design StyleCastor6/tactus	376	1 repos	~2.1k	Automated safety check: Pass	Apache-2.0	5 mo ago
Shadcn Svelteexceptionless/Exceptionless	2.5k	—	~3.6k	Automated safety check: Pass	Apache-2.0	today
Svelte Code Writerkampsy/ui	288	3 repos	~490	Automated safety check: Pass	MIT	9 days ago
Kampsy UIkampsy/ui	288	—	~3.6k	Automated safety check: Pass	MIT	9 days ago

Similar skills

UI/UX Design System Advisor
Galaxy-Dawn/claude-scholar
Turns a vague UI request into a concrete design system with style, palette, typography and layout guidance from a search script, plus stack-specific implementation advice.
5.7k GitHub starsUsed in 1 repo~1.1k tokens
Frontend & DesignAuto-check passed
Design Style
Castor6/tactus
A skill your agent uses whenever the user asks to build, create, design, develop, improve, or style any frontend interface or visual element.
376 GitHub starsUsed in 1 repo~2.1k tokens
Frontend & DesignAuto-check passed
Shadcn Svelte
exceptionless/Exceptionless
Manages shadcn-svelte components and projects — adding, updating, fixing, debugging, styling, and composing UI.
2.5k GitHub stars~3.6k tokensUpdated today
Frontend & DesignAuto-check passed
Svelte Code Writer
kampsy/ui
CLI tools for Svelte 5 documentation lookup and code analysis.
288 GitHub starsUsed in 3 repos~490 tokens
Frontend & DesignAuto-check passed
Kampsy UI
kampsy/ui
Consumer guide to build UIs with kampsy-ui (Svelte 5 + Tailwind v4, Geist-inspired).
288 GitHub stars~3.6k tokensUpdated 9 days ago
Frontend & DesignAuto-check passed
UI UX Pro Max
sundial-org/awesome-openclaw-skills
UI/UX design intelligence and implementation guidance for building polished interfaces.
663 GitHub starsUsed in 2 repos~657 tokens
Frontend & DesignAuto-check passed

Questions about UI Components

What does UI Components do?

UI Component Development Guide for Kaiden. An agent skill from openkaiden/kaiden. UI Components is an agent skill from openkaiden/kaiden.

When should I use UI Components?

UI Components fits situations like: tasks that involve Design systems.

How do I install UI Components in Claude Code?

Run `npx skills add openkaiden/kaiden --skill ui-components -a claude-code`. Or copy the skill folder (.agents/skills/ui-components in openkaiden/kaiden) into .claude/skills/ui-components in your project. Claude Code loads it when a task matches its description.

How do I install UI Components in Codex?

Run `npx skills add openkaiden/kaiden --skill ui-components -a codex`. Or copy the skill folder (.agents/skills/ui-components in openkaiden/kaiden) into .agents/skills/ui-components in your project. Codex loads it when a task matches its description.

Can I use UI Components 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 openkaiden/kaiden --skill ui-components -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-components, .gemini/skills/ui-components, .github/skills/ui-components and .opencode/skills/ui-components in your project.

What does UI Components need to run?

SKILL.md names no scripts, command-line tools or credentials: UI Components is instructions for the agent only.

Does UI Components access the network?

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.

Is UI Components 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 UI Components use?

UI Components is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does UI Components use?

About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to UI Components?

Skills that share tags, products or a category with UI Components: UI/UX Design System Advisor (Galaxy-Dawn/claude-scholar, 5.7k stars), Design Style (Castor6/tactus, 376 stars), Shadcn Svelte (exceptionless/Exceptionless, 2.5k stars) and Svelte Code Writer (kampsy/ui, 288 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains UI Components?

openkaiden (a GitHub organization) maintains it in openkaiden/kaiden, which has 110 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 8, 2026.

Source: openkaiden/kaiden on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

UI Components

Install UI Components

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

UI Component Development Guide for Kaiden

Core Rules

1. Check `@podman-desktop/ui-svelte` before building from scratch

2. Never use Tailwind colors directly

3. Use the Icon component for all icons

4. Reuse existing Kortex Svelte components

How the Color Registry Works

Finding the right color variable

Common color categories and prefixes

Example: Styling a new component

Files

Compare with similar skills

Similar skills

UI/UX Design System Advisor

Design Style

Shadcn Svelte

Svelte Code Writer

Kampsy UI

UI UX Pro Max

More from openkaiden/kaiden

Create GitHub Issue

Playwright Testing

Questions about UI Components

Install UI Components

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

UI Component Development Guide for Kaiden

Core Rules

1. Check @podman-desktop/ui-svelte before building from scratch

2. Never use Tailwind colors directly

3. Use the Icon component for all icons

4. Reuse existing Kortex Svelte components

How the Color Registry Works

Finding the right color variable

Common color categories and prefixes

Example: Styling a new component

Files

Compare with similar skills

Similar skills

More from openkaiden/kaiden

Related

Questions about UI Components

1. Check `@podman-desktop/ui-svelte` before building from scratch