components

UI component patterns for React 19, shadcn/ui, and Tailwind. Use when working on files in src/components/.

⭐2stars🔀0forks📁View on GitHub🕐Updated Jan 11, 2026⬇️2downloads

When & Why to Use This Skill

This Claude skill streamlines React 19 development by enforcing standardized UI component patterns using shadcn/ui and Tailwind CSS. It ensures high-quality code consistency, accessibility, and performance across the src/components/ directory, covering everything from advanced state management to dark mode implementation.

Use Cases

  • Developing accessible React 19 components with semantic HTML, ARIA labels, and keyboard navigation support.
  • Implementing consistent styling using Tailwind CSS and shadcn/ui design tokens with built-in dark mode compatibility.
  • Optimizing component performance through strategic use of useMemo, useCallback, and list virtualization.
  • Managing complex UI states using local hooks, CRDT-based data mutations, and URL-persistent filters.
  • Standardizing component architecture with JSDoc documentation and unified prop interfaces.
namecomponents
descriptionUI component patterns for React 19, shadcn/ui, and Tailwind. Use when working on files in src/components/.

Components Guidelines

Patterns

  • "use client" only if using hooks/interactivity
  • Export interface with Props suffix, document props with JSDoc
  • Always include optional className prop, use cn() for merging

Styling

  • Tailwind only - no CSS modules or styled-components
  • Use shadcn/ui tokens: text-muted-foreground, bg-background, etc.
  • All components must support dark mode via dark: prefix

State

  • Local: useState for UI-only state (dropdowns, modals)
  • CRDT: useVaultAction/useActiveTransactions for data mutations
  • URL: useSearchParams for filters that should persist

Performance

  • useMemo/useCallback for expensive computations and callbacks to memoized children
  • Virtualize long lists (TransactionTable already does this)
  • Avoid inline object/array literals in JSX props

Accessibility

  • Semantic HTML, aria-labels on icon-only buttons
  • Keyboard navigation, focus management in modals