Repo of the Day
vprix21/neonblade-ui
Published: Mar 28, 2026
Open repository ↗Contribute to vprix21/neonblade-ui development by creating an account on GitHub.
Summary
NeonBlade UI is a React + TypeScript component library that delivers futuristic, neon, and cyberpunk-styled UI primitives for the web. Instead of being a traditional npm dependency, it ships components via a CLI that copies the source into your project, giving engineers full control over styling and behavior.
What it is useful for
Building interfaces that want a strong sci-fi or neon visual identity without writing every glow, scanline, or animated surface from scratch. It fits marketing pages, dashboards for developer tools, game-adjacent apps, and demos where a conventional design system feels too plain. Because components are added individually and live in your codebase, it works well when you want specific futuristic pieces (like the ascii-rain example) without adopting an entire system. The library is also useful as a reference for animation patterns built on Framer Motion and Three.js.
How engineers can use it
Add a component to an existing app with npx neonblade add <component-name> — for example, npx neonblade add ascii-rain. Running npx neonblade add with no name lists every available component. The CLI fetches manifests from https://neonbladeui-registry.vercel.app, writes component files into the host project, and installs required dependencies automatically. Components are styled with Tailwind CSS v4 and animated using Framer Motion, so a Tailwind v4 setup in the host app is effectively required.
To run the docs site or contribute, the README lists Node.js 18+ and pnpm 9+ as prerequisites, then pnpm install followed by pnpm dev to start everything. pnpm build, pnpm lint, pnpm check-types, and pnpm format are also documented. The README does not include per-component API or prop documentation, so the website at neonbladeui.neuronrush.com is the reference for usage specifics. Because the CLI pulls from a remote registry, an outage of neonbladeui-registry.vercel.app would block new component installs, which is worth noting for production workflows.