I built a 659-component React library with a Ticket-Stub soul (MIT, zero deps)
Most component libraries look the same. I wanted one that feels like something — a well-printed admission ticket: warm cream paper, ink lines, a red rubber stamp. That's bigbullui, now at v1.2.0.
What it is: 659 copy-paste React 19 + Tailwind v4 components, 63 page blocks, 1023 hand-drawn stroke icons. Zero runtime dependencies — every file imports only react and a 7-line cn helper. MIT, no attribution needed.
Three ways to use it:
npx bigbullui add ticket-card # steal one component
npm i bigbullui # take the package
npx shadcn@latest add https://ui.bigbullapp.com/r/button.json # shadcn CLI works too
Blocks work the same way (.../r/admin-overview.json bundles the block plus its components), and npx create-bigbull-app my-app scaffolds a starter.
For the AI-coding era: it ships an MCP server so Cursor/Claude Code can list components, fetch source, and read theme tokens directly — no backend, it runs locally:
claude mcp add bigbullui -- npx -y bigbullui mcp
Try before you install: /create — pick components, icons, and a theme, get one install command. Or browse all 659.
Built in the open, feedback welcome — what's missing for your stack?
Top comments (1)
Shipping an MCP server directly with the component library is a massive shift for how we handle design system adoption. Usually, engineers waste context window space pasting raw component code into Claude just to establish the baseline patterns, but exposing the source and theme tokens locally completely bypasses that friction. It essentially turns the UI kit into a native primitive for the AI. Are you finding the LLM hallucinates less with Tailwind v4 classes when it has direct access to the source code through the server?