introduction

chrome is a dark-only component registry in the shadcn mold: you don't install a package, you install source. the cli copies each component's code into your project under components/chrome/, and from then on it's yours — read it, restyle it, rip parts out. there is no runtime dependency on this site.

the components port the design language of justin06lee.dev: black backgrounds, 1px borders, square corners, lowercase copy, restrained motion. they're framework-agnostic react — plain anchors instead of router links, tailwind v4 for styling, and any css a component needs travels inside its own file.

quick start

in any next.js + tailwind v4 project:

# one-time setup: writes chrome.json, lib/utils.ts, patches globals.css
bunx @justin06lee/chrome@latest init


# then add components as you need them
bunx @justin06lee/chrome@latest add button dialog command-palette

add resolves component-to-component dependencies transitively — adding command-palette also brings kbd; adding desk pulls the whole editor suite. npm dependencies are unioned and installed in one pass.

browsing

every component page has a live demo, copyable usage variants, and a props table. the sidebar has search, or press ⌘k anywhere to jump straight to a component.

next