AGENT SKILL

ui-reference

UI component library reference guide. Use when building UI without a design, choosing a component library, or looking for animation/effect inspiration. Covers headless, styled, animation, and chart libraries with llms.txt links for AI-readable documentation.

适用职业设计师
使用场景视觉设计
License 许可
MIT
最近更新
2026-03-27
Stars
★ 3
Forks
1

01 前言 Front Matter

name
ui-reference
description
UI component library reference guide. Use when building UI without a design, choosing a component library, or looking for animation/effect inspiration. Covers headless, styled, animation, and chart libraries with llms.txt links for AI-readable documentation.

02 资源文件 1

03 SKILL.md 正文

UI Reference

When you need to build UI without a Figma design, or need inspiration for components, animations, or effects — reference these libraries. Each entry includes an AI-readable documentation link (llms.txt) when available.

When to Use This Reference

  • Feature has no Figma design and you need UI component patterns
  • Need animation or visual effect ideas for an existing component
  • Choosing between component libraries for a new project
  • Looking for a specific component type (chart, drag-and-drop, date picker, etc.)
  • Need to understand a library's API before implementing

Quick Selection Guide

Need Recommended Why
Headless + full custom styling Base UI, Ark UI Zero style opinions, bring your own CSS
shadcn/ui ecosystem extension ReUI, coss ui, Bklit UI Built for shadcn, same patterns
Tailwind + ready-to-use HeroUI, DaisyUI Pre-styled with Tailwind
Enterprise/admin dashboard Ant Design, Mantine Rich component set, tables, forms
Animation effects Animata, ReactBits Copy-paste animated components
AI-assisted component generation 21st.dev AI generates custom components
Charts / data visualization Bklit UI shadcn-compatible chart components

Headless (Unstyled) Libraries

Base UI

  • Type: Headless component library (40+ components)
  • Styling: Bring your own — works with Tailwind, styled-components, CSS Modules, anything
  • Best for: Custom design systems where you need full control. Ideal with shadcn/ui for building custom component libraries
  • llms.txt: https://base-ui.com/llms.txt
  • Pros: Zero style opinions, excellent accessibility, composable API
  • Cons: Must write all styles yourself, React only

Ark UI

  • Type: Headless component library (50+ components)
  • Styling: Framework-agnostic, bring your own
  • Best for: Multi-framework projects (React, Vue, Svelte, Solid)
  • llms.txt: https://ark-ui.com/llms.txt
  • Pros: Same API across 4 frameworks, MCP server support, extensive primitives
  • Cons: Smaller community than Radix

Styled (Tailwind-based) Libraries

HeroUI

  • Type: Styled component library (210+ components)
  • Styling: Tailwind CSS + tailwind-variants, build-time CSS
  • Best for: Next.js projects that want beautiful defaults with Tailwind customization
  • Docs: https://www.heroui.com/docs/guide/introduction
  • Pros: Large component count, Framer Motion animations built-in, dark mode, successor to NextUI
  • Cons: React only, heavy dependency on Tailwind + React Aria

DaisyUI

  • Type: CSS component classes for Tailwind (50+ components)
  • Styling: Tailwind class-based, semantic color system
  • Best for: Quick prototyping, framework-agnostic (works with any HTML)
  • llms.txt: https://daisyui.com/llms.txt
  • Pros: Framework-agnostic (HTML classes), built-in themes, zero JS dependency
  • Cons: Less interactive behavior (CSS-only), limited complex components

shadcn/ui Ecosystem

ReUI

  • Type: Enterprise-grade shadcn registry (18+ advanced components)
  • Styling: shadcn + CSS variable design tokens
  • Best for: Data tables, forms, drag-and-drop, date pickers in shadcn projects
  • llms.txt: https://reui.io/llms.txt
  • Pros: Dual primitive support (Base UI + Radix), MCP server, enterprise quality
  • Cons: Smaller component set, shadcn dependency

coss ui

  • Type: Hybrid — Base UI + Tailwind styled (50+ components)
  • Styling: Tailwind CSS on Base UI headless foundation
  • Best for: Migration from shadcn/Radix, wanting headless flexibility with pre-styled defaults
  • llms.txt: https://coss.com/ui/llms.txt
  • Pros: Migration guides from shadcn/Radix, own-your-code model, accessibility-first
  • Cons: Relatively new, smaller ecosystem

Bklit UI

  • Type: Chart/data visualization components for shadcn (11+ chart types)
  • Styling: CSS custom properties, shadcn theming
  • Best for: Adding charts (line, bar, pie, candlestick, sankey, etc.) to shadcn projects
  • Docs: https://ui.bklit.com/docs/installation
  • Pros: Auto-registry config, animated transitions, real-time data support
  • Cons: Charts only, not a general component library

Full-featured Libraries

Chakra UI

  • Type: Styled component library (v3)
  • Styling: CSS-in-JS with theming system
  • Best for: Rapid development with good defaults and strong accessibility
  • llms.txt: https://chakra-ui.com/llms.txt
  • Pros: Excellent DX, comprehensive theming, active community
  • Cons: CSS-in-JS runtime cost, less Tailwind-friendly

Ant Design

  • Type: Enterprise styled library (60+ components)
  • Styling: CSS-in-JS with token system, dark mode
  • Best for: Admin dashboards, enterprise backend systems, data-heavy UIs
  • llms.txt: https://ant.design/llms.txt
  • Pros: Most comprehensive component set, battle-tested at scale, i18n
  • Cons: Opinionated design, large bundle, enterprise aesthetic

Mantine

  • Type: Full-featured React library (100+ components + hooks + extensions)
  • Styling: CSS Modules, Emotion, Sass, vanilla-extract supported
  • Best for: Projects needing components + hooks + charts + rich text editor in one ecosystem
  • llms.txt: https://mantine.dev/llms.txt
  • Pros: Hooks ecosystem, date/chart/notification/carousel extensions, CSS variable theming
  • Cons: Large dependency surface, React only

Animation & Effects

Animata

  • Type: Copy-paste animated React components (150+ elements)
  • Styling: Tailwind CSS + Framer Motion
  • Best for: Adding micro-interactions, animated cards, hero sections, text effects
  • Docs: https://animata.design/docs/setup
  • Pros: No npm install needed (copy-paste), 20+ categories, Tailwind native
  • Cons: Must copy each component manually, quality varies

ReactBits

  • Type: Visual effects library (100+ components in 4 variants)
  • Styling: JS+CSS, JS+Tailwind, TS+CSS, TS+Tailwind variants
  • Best for: Advanced visual effects — particle systems, 3D interactions, WebGL backgrounds, text animations
  • llms.txt: https://reactbits.dev/llms.txt
  • Pros: GSAP + Three.js + Framer Motion powered, 4 variant options, CLI installable
  • Cons: Heavy effects may impact performance, advanced usage requires WebGL knowledge

AI-Assisted

21st.dev

  • Type: AI component generation platform
  • Styling: React + Tailwind output
  • Best for: Generating custom components when no design exists, browsing community component library
  • llms.txt: https://21st.dev/llms.txt
  • Pros: IDE integration (Cursor/Windsurf), component marketplace, craft-focused output
  • Cons: Credit-based pricing, generated code needs review

Usage with NCC Agents

When an agent needs UI reference:

  1. Check if the project already uses a component library (spec/PROJECT.md ## Libraries)
  2. If yes — use that library's llms.txt for component API reference
  3. If no design exists — use this guide to pick appropriate components
  4. For animations/effects — check Animata and ReactBits before writing custom animations
  5. Pass the llms.txt URL to WebFetch for detailed API documentation

04 同仓库更多 Skills

ByeongminLee
ByeongminLee/nextjs-claude-code

zustand

Zustand state management guide. Use when working with store code (src/store/**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.

★ 3
ByeongminLee
ByeongminLee/nextjs-claude-code

web-vitals

暂无简介

★ 3
ByeongminLee
ByeongminLee/nextjs-claude-code

vercel-storage

Vercel storage expert guidance — Blob, Edge Config, and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.

后端与接口
★ 3
ByeongminLee
ByeongminLee/nextjs-claude-code

vercel-functions

Vercel Functions expert guidance — Serverless Functions, Edge Functions, Fluid Compute, streaming, Cron Jobs, and runtime configuration. Use when configuring, debugging, or optimizing server-side code running on Vercel.

开发工程师后端与接口
★ 3
ByeongminLee
ByeongminLee/nextjs-claude-code

ui-ux-pro-max

UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, and flat design. Topics: color systems, accessibility, animation, layout, typography, font pairing, spacing, interaction states, shadow, and gradient. Integrations: shadcn/ui MCP for component search and examples.

设计师数据分析师前端开发视觉设计
★ 3
ByeongminLee
ByeongminLee/nextjs-claude-code

turborepo

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.

★ 3