Agent Skills › panel-ui/PanelUI › panelui-web

panelui-web

GitHub

用于在已配置 shadcn/ui 的 React 项目中构建 PanelUI Web UI。通过组合主题化组件（如面板、图表）生成前端界面，严格遵循颜色语义、数据分离及无障碍规范。

skills/panelui-web/SKILL.md panel-ui/PanelUI

Trigger Scenarios

用户要求在 React 项目中创建 PanelUI 风格的前端界面提及使用 PanelUI 组件（如 KPI 卡片、看板、节点图）进行开发

Install

npx skills add panel-ui/PanelUI --skill panelui-web -g -y

More Options

Use without installing

npx skills use panel-ui/PanelUI@panelui-web

指定 Agent (Claude Code)

npx skills add panel-ui/PanelUI --skill panelui-web -a claude-code -g -y

安装 repo 全部 skill

npx skills add panel-ui/PanelUI --all -g -y

预览 repo 内 skill

npx skills add panel-ui/PanelUI --list

SKILL.md

Frontmatter

{
    "name": "panelui-web",
    "license": "MIT",
    "metadata": {
        "author": "Khalid Abdi",
        "version": "0.3.0"
    },
    "description": "Build React web UIs with PanelUI's web collection — adding its components from the shadcn registry or from npm, colouring them from the theme, and composing them into framed panels. Applies when working in a React project that has shadcn\/ui set up with a @panelui registry or has panelui-web installed, when the user mentions PanelUI on the web, or when they ask for a dotted globe, a KPI card, a kanban board, a node graph, an activity grid or a feedback dialog in React.",
    "allowed-tools": "Bash(npx shadcn@latest *), Bash(pnpm dlx shadcn@latest *), Bash(bunx shadcn@latest *)",
    "compatibility": "React 19 with Tailwind CSS v4 and shadcn\/ui tokens. Not for React Native — the app library is a separate skill, panelui."
}

PanelUI for the web

Components for React, built on shadcn/ui. They are styled with Tailwind CSS v4 on the theme tokens a shadcn project already has, so they take the project's colours, radii and dark mode without any setup of their own.

This is the web collection. PanelUI's React Native library is a different package with a different skill; nothing here runs in React Native.

Before writing any UI

Read components.md to see what exists. Use a component from it before writing a custom one.
Read the component's own file in components/ before using it. It has the import line, every part and every prop, read from the source. Do not guess a prop.
Check how the project installs: a components.json with a @panelui registry means components are copied in with the shadcn CLI; panelui-web in package.json means they are imported from the package. See setup.md.

Rules

Colour is a role, never a value. Every component that has a colour takes color="primary" | "info" | "success" | "warning" | "destructive". Do not pass hex values or Tailwind palette classes for a component's own colour. See theming.md.
Pick the role by meaning. success for good, warning for attention, destructive for bad, info for neutral emphasis, primary otherwise. Do not give every component on a screen the same colour.
Give data its own text. Labels, counts and names in a component come from the project's data. Do not reuse the sample text from these files.
Compound parts and Server Components. In a file with "use client", write parts with a dot: Planet.Globe. A Server Component cannot read a property off a client module, so there every part is imported by name: PlanetGlobe. Kpi is not a client module and can be dotted anywhere.
Lead with a frame. A component shown as a panel sits in a frame: a muted band with a title, round an inner bordered card. See the examples in each component's file.
Label what a screen reader needs. Components take label, and where a value is shown, valueText. Pass them: the defaults are generic.