shadcn/ui is a React component library and CLI tool that provides beautifully designed, copy-paste UI components for building modern web applications. The repository is a monorepo containing a Next.js documentation site (apps/v4) that showcases hundreds of components, examples, blocks, and a design system customizer, along with a CLI package (packages/shadcn) for scaffolding components into user projects. The architecture is organized around multiple style bases (React Aria, Base UI, Radix UI) and a registry system that defines components, hooks, utilities, and blocks as typed JSON items. Key entry points include the CLI commands (add, init, build, migrate, search, view) and the Next.js app routes for documentation, examples, blocks, charts, and the interactive design system creator. External dependencies include React, Tailwind CSS, various UI primitives (react-aria-components, @base-ui/react, @radix-ui/react-*), Recharts for charts, next-themes for dark mode, and several icon libraries (lucide, tabler, hugeicons, phosphor, remixicon). Data flows involve fetching registry items from a remote or local source, transforming them (import rewriting, CSS variable injection, RTL adaptation), and adding them to the user's project. The design system customizer encodes configuration into compact base62 preset codes that can be shared and applied.
Radix Themes is a monorepo containing a React component library built on Radix UI primitives and a Next.js playground application for demonstration and testing. The library provides accessible, themeable UI components with support for responsive values, variant styling, and a flexible theme system. The architecture separates concerns through a prop definition system, helper utilities for style extraction and merging, and a theme context. The playground showcases components and includes visual regression testing via Playwright.
react-native-reusables is a React Native UI component library that adapts the shadcn/ui copy-paste component model to React Native. It is a pnpm/Turborepo monorepo containing a Next.js/Fumadocs documentation site (apps/docs), an Expo SDK 56 showcase app for live cross-platform previews (apps/showcase), a scaffolding CLI built on Effect-TS (apps/cli), and a shared registry package (packages/registry) with roughly 30 styled components — Button, Dialog, Select, Accordion, Dropdown Menu, Tooltip, and others — plus higher-level authentication blocks (sign-in, sign-up, forgot/reset password, verify email) with optional Clerk integration. There is no data science or analytics code; it is purely a component library and developer-tooling project. The central architectural decision is dual styling-engine support: every component is implemented twice, once for Nativewind and once for Uniwind, both wrapping @rn-primitives (Radix-style primitives ported to React Native). Components use class-variance-authority for variant management, a Slot primitive for asChild composition, a TextClassContext that propagates text styles down component hierarchies (a non-obvious workaround for React Native's lack of CSS style cascading), and a portal/overlay system that uses iOS FullWindowOverlay on native platforms and fragments on web. The target platforms are iOS, Android, and web via Expo. Component source is serialized into shadcn-compatible registry JSON files (public/r/nativewind/*.json and public/r/uniwind/*.json) consumed by both the docs site and the CLI, with catalogs.dev YAML metadata driving publishing and discoverability. The CLI's init/add/doctor commands wrap the shadcn installation machinery with additional project intelligence: the doctor command validates dependencies and detects deprecated file patterns, and project-config.ts parses a project's metro.config.js to determine whether Nativewind or Uniwind is active before writing components.json. The add command delegates component installation to shadcn. Several auth blocks contain explicit TODO placeholders for navigation and form-submission logic that consumers must implement. The dominant maintenance burden is the deliberate duplication across the two styling engines — every API or visual change must be mirrored in both variants, and the generated registry JSON can drift from source files. Dependencies (Expo SDK 56, React Native 0.85.3, Nativewind 4.2.2, Uniwind 1.6.3) are current, and the repo tracks its ecosystem proactively.
A collection of reusable React UI components built on top of shadcn/ui (Radix UI + Tailwind CSS), along with a Next.js documentation site. The project provides 15+ advanced components not included in the base shadcn/ui library, such as a datetime picker with keyboard navigation, a multiple-selector with async search and grouping, an interactive stepper, infinite scroll, and others. All components are designed to be copied and pasted directly into user projects and are fully customizable. The documentation site demonstrates each component with live previews, usage examples, and prop tables. The codebase is well-structured, modern (Next.js 15, React 19, TypeScript), and actively maintained.
This is the monorepo for Supabase, the open-source Firebase alternative built on PostgreSQL. The repository contains the complete Supabase platform including: (1) Studio - a Next.js-based management dashboard for database, auth, storage, and edge functions, (2) Docs - a Next.js documentation site with MDX content and search, (3) WWW - the main marketing website, (4) UI packages - shared React component libraries built on Radix UI and Tailwind CSS, (5) pg-meta - a TypeScript library for PostgreSQL metadata introspection, (6) ai-commands - AI/LLM integration tools, (7) Docker configurations for self-hosted deployments, and (8) numerous example applications demonstrating Supabase integrations. The architecture is a pnpm monorepo using Turbo for build orchestration. The codebase demonstrates sophisticated engineering patterns including: a custom SQL query builder with branded types for safe SQL composition (pg-meta), a comprehensive component library with design system tokens, real-time features via WebSockets, row-level security policy management, and a multi-tenant organization/project structure. The repository is actively maintained with recent commits and has strong community engagement (105k+ stars).
BlazorBlueprint is a comprehensive Blazor UI component library inspired by shadcn/ui, providing over 112 styled components and 28 headless primitives. It targets .NET 8 across Server, WebAssembly, and Auto render modes, with full accessibility (ARIA, keyboard navigation), theming via CSS custom properties (compatible with shadcn CSS variables), and zero Tailwind/Node setup. The library is split into two layers: Primitives (headless, behavioral components with focus management, positioning, and portal services) and Components (styled, ready-to-use widgets like DataGrid, charts, forms, dialogs, and navigation). It ships with four icon libraries (5,200+ icons) and 11 chart types via Apache ECharts. The architecture emphasizes composability through cascading contexts, a consistent form-field pattern, and a utility-first approach with the ClassNames.cn helper for Tailwind class merging. The codebase demonstrates strong engineering practices: extensive use of generics, expression trees for filtering, JS interop with guarded disposal, and a localization system with 200+ string keys. However, the large API surface, heavy JS interop, and limited test coverage (only a few unit tests for DataGrid and hierarchy utilities) present maintenance risks.
This repository contains the source code for a personal link-in-bio website (moure.dev) built with the Reflex Python web framework. It serves as both a live production site and a practical example for a 13-hour web development course. The application is a full-stack Python app with a static frontend (React/Reflex) and a Dockerized backend. It integrates multiple external APIs: Twitch (live status), Supabase (featured content), ConfigCat (feature flags), and Beehiiv (newsletter). The architecture follows a component-based design with reusable UI elements (link buttons, cards, navbar, footer) and a centralized state management pattern. The frontend is exported as static HTML/JS and hosted on Vercel, while the backend runs on Railway. The code is well-structured, uses modern Reflex with Radix UI, and includes deployment scripts and a GitHub Actions CI pipeline. It is primarily a learning resource and a functional personal site, not a generic library or framework.