What you get

Component code that lives in your repo, editable down to the markup, with no release to wait for.

shadcn/ui: Components You Copy, Then Own

Added 2026-08-06

Not an npm dependency — the component source lands in your repo and becomes yours to edit. The project's own framing: start here, then make it your own component library.

Engineering

View on GitHub ↗

shadcn/ui: Components You Copy, Then Own preview

The README is three sentences and the stance is clear: open source, open code, use it to build your own component library. Distribution is source-copy rather than version pinning — once a component is in your repo it is your file, free to restyle or rewrite, with no upstream version constraining it. The cost sits at the other end: upstream improvements don't flow down on their own, and whether to take them is your call. Docs at ui.shadcn.com, MIT licensed.

Related skills

Taste Skill: The Anti-Slop Layer for AI-Built UIPortable agent skills aimed at the sameness of AI-generated interfaces — stronger layout, typography, motion and spacing. A separate set generates reference imagery only, no code.Design & Video · Engineering72.6K stars Small, Hackable Skills for Real EngineeringThe skills Matt Pocock uses daily: get grilled until nothing is ambiguous, turn talk into a spec and linked tickets, build red-green-refactor, run hard bugs through a fixed loop. Small and hackable, not process-owning.Engineering · Product & Project205.2K stars 24 Engineering Skills, /spec Through /shipEight slash commands along the development lifecycle — spec, plan, build a slice at a time, test, review, webperf, simplify, ship — plus skills that self-activate: API work pulls in interface design, UI work in frontend.Engineering82K stars The Delivery Chain From Local Project to Public URLSeven fixed steps: check CLI logins, build locally, push to GitHub, connect and deploy on Vercel, add the domain, write DNS at Cloudflare, verify, and curl for HTTPS at the end.Engineering · Product & Project17 stars