Introduction
NeonKit is 139 React components for dark interfaces, lit like signage after hours, plus 60 blocks and 5 templates built from them. You don't install it as a dependency: you add the files you want and they become part of your project.
How it works
Add a component with the shadcn CLI or paste its source. It lands in components/ui next to two small helpers: cn for merging classes and neonVars for color. This is the whole idea, running:
Principles
- The code is yours
- No package to update and no wrapper to fight. Each component is one file in your repo, and you can change any line of it.
- One variable sets the color
- Every component reads --neon. Pass color, set it on a parent, or leave it alone and get cyan.
- Light means something
- Resting UI stays calm. Glow shows up for focus, selection, hover and progress, so when something lights up, it's telling you why.
- It fits your stack
- React 18 or 19, Tailwind 3.4 or 4, Next.js, Vite or Remix. Native elements and the keyboard come first.
Why not a package?
UI libraries tend to end up as a pile of overrides. When the code lives in your repo, you edit the component itself and see every class it ships with. It's the same idea as shadcn/ui, and NeonKit plugs into its CLI, so the two sit side by side in one components/ui folder.
Start with installation, or go straight to the components and copy one.