Loading...
Loading...
Found 39 Skills
Build bulletproof React components that survive SSR, hydration, concurrent rendering, portals, transitions, and future React changes. Nine essential patterns from Shu Ding's guide. Use when writing reusable React components, fixing hydration mismatches, handling SSR edge cases, or building component libraries.
Creates unstyled compound components that separate business logic from styles. Use when building headless UI primitives, creating component libraries, implementing Radix-style namespaced components, or when the user mentions "compound components", "headless", "unstyled", "primitives", or "render props".
Best practices for building and documenting component libraries with Storybook
Use when building documentation sites with live code previews, component library docs, API reference pages, or interactive code examples using Next.js App Router and shadcn/ui.
Build or evolve a design system by producing a Design System Operating Pack: charter, token model (incl. depth/elevation), component inventory + roadmap, blockframe-to-component mapping, documentation plan, and governance/adoption plan. Use for design systems, component libraries, design tokens, UI kits, and pattern libraries.
Figma REST API for accessing design files, comments, components, and projects. Use this skill to read file contents, export images, manage comments, and integrate with Figma workspaces.
Skill for building platform-independent design systems. Develops consistent component libraries for all UI frameworks. Use proactively when user needs consistent UI components or mentions design tokens. Triggers: design system, component library, design tokens, shadcn, 디자인 시스템, デザインシステム, 设计系统, sistema de diseño, biblioteca de componentes, tokens de diseño, système de design, bibliothèque de composants, jetons de design, Design-System, Komponentenbibliothek, Design-Tokens, sistema di design, libreria di componenti, token di design Do NOT use for: one-off UI changes, backend development, or simple static sites.
This skill should be used when the user asks to "create a design system", "build a design system for [business]", "design a UI kit", "create components in Pencil", "build screens for [industry]", "set up design tokens", or wants to generate a comprehensive, domain-tailored design system with variables, themes, reusable components, and example screens in a .pen file. Also triggered by "design system from scratch", "build a component library", or "create themed UI for [business type]".
Expert-level Atomic Design System development from Figma style guides. Build reusable component libraries with atoms, molecules, organisms, templates, and pages.
Design interfaces following Google's Material Design system, the unified visual language bridging digital and physical worlds. Emphasizes bold graphic design, intentional motion, adaptive layouts, and the material metaphor. Use when building modern, accessible, delightful user interfaces across platforms.
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture.
DaisyUI 5 component library best practices, patterns, and usage for Tailwind CSS 4. Use when building UI with daisyUI class names, creating daisyUI-based layouts, styling HTML with daisyUI components, creating React wrapper components for daisyUI, or any task involving daisyUI (.html, .jsx, .tsx, .vue, .svelte files). Triggers on: daisyUI components (btn, card, modal, drawer, navbar, etc.), daisyUI color names (primary, secondary, base-100, etc.), daisyUI config (@plugin "daisyui"), daisy-meta.ts, generate-daisy-safelist, compound components wrapping daisyUI, or any UI task in a project using daisyUI/Tailwind CSS 4.