Manage shadcn/ui components: add, search, fix, style and compose, with registry and component docs. Applies to any project with a components.json. Triggers on "shadcn init" or a --preset code.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# shadcn/ui
A framework for building ui, components and design systems. Components are added as source code to the user's project via the CLI.
> **IMPORTANT:** Default shadcn runner: `bunx --bun shadcn@latest`. In pnpm repos, use `pnpm dlx shadcn@latest`; with npm, `npx shadcn@latest`; with Yarn, `yarn dlx shadcn@latest`. Detect via `packageManager`, then lockfile. Examples use Bun; substitute the project runner throughout, including the `info --json` step below.
## Current Project Context
Select the package runner using the IMPORTANT line above, then load the
project config and installed components with `<runner> info --json`. With the
default Bun runner the context is already injected below:
```json
!`bunx --bun shadcn@latest info --json`
```
The resulting JSON contains the project config and installed components. If
the injected result below is an error (e.g. Bun is not installed), run
`<runner> info --json` with your selected runner instead. Use
`<runner> docs <component>` to get documentation and example URLs for any
component.
## Principles
…
The line at the top of this page pins the label git:20260908.2a5535e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_elcudjqprdlvt3bt
GET https://markdownregistry.com/api/v1/resolve?ref=bjornmelin/dev-skills/shadcn
GET https://markdownregistry.com/api/v1/blob/b94083ccf3fd4693211e2b84d74631f79615317332f8ac7b9e9fa343cdfac3ad
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
bjornmelin/dev-skills · archive/skills/browser-workbench-setup/SKILL.md · Set up browser automation and UI QA for a new repository using playwright-interactive as the primary interactive tool…
bjornmelin/dev-skills · archive/skills/bun-audit/SKILL.md · Shared Bun audit/remediation router. Use when auditing a repo for Bun-first correctness, explaining findings, listing…
bjornmelin/dev-skills · archive/skills/managing-tech-debt/SKILL.md · Help users manage technical debt strategically. Use when someone is dealing with legacy code, planning refactoring…
